Attachment 919782 Details for Bug 1121816 – Email from Don with suggested improvements

Email from Don with suggested improvements

TransitionGuide-donf.txt (text/plain), 10.67 KB, created by David O'Brien on 2014-07-22 01:22:11 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: David O'Brien

Created: 2014-07-22 01:22:11 UTC

Size: 10.67 KB

patch

obsolete

>Hi David/Athene, I am on the sat-sme team, and I was going to work on a comparison guide between satellite 5 and 6 for SAs.  I found your transition guide, which I thought looks great. I was reviewing the doc, and I made a few suggestions below.  Please feel welcome to use if you think they are relevant.
>
>For the beginning satellite 5 and satellite 6 intros in chapter 1.
>
>1.1
>
>Red Hat Satellite 5 is life cycle management tool that includes the capabilities to deploy, manage and monitor a large number of systems.  Satellite 5 can be set-up in a connected or disconnected mode in which Red Hat software is distributed to client systems using the original pooled subscription approach. The pooled subscription concept is similar to the way in which clients consume entitlements from the classic Red Hat Network.  For more information on classic Red Hat Network, see the following link "" 
>
>The popular functionality of satellite 5 included the ability to provision a large number of systems utilizing a kickstart files and activation keys to install and configure systems to a predictable state. This provisioning process associated systems to a designated organizations, software and configuration channels as well as placed systems within predefined systems group and or groups.  The Satellite 5 provisioning functionality enabled administrators to provision thousands of systems in a consistent manner.
>
>Once systems are provisioned another popular functionality is the ability to manage software and configuration files across large numbers of systems in local or remote environments.  One of the really well understood concepts of managing software and configuration files in satellite 5 is the concept of channels. All software and configurations are managed and distributed through channels, and any client needing access to software or configuration content would need to be associated to the one or many relevant channels.  Additionally, channel cloning capability enabled admins to create the much needed development-production environments required by most enterprises. 
>
>While satellite 5 is well know for providing a solid platform for managing software and configurations files for a large number of systems and also well known for the simplicity and consistency of the provisioning process, the satellite 5 systems management platform is also well known for delivering the correct versions and updated versions of content to the correct systems in a very structured manner. Administrators managed the satellite and systems management processes through the satellite webui and also satellite api interfaces.
>
>1.2 
>
>Red Hat Satellite 6 is the evolution of Red Hat's life cycle management platform.  It provides the capabilities that administrators have come to expect in a tool focused on managing systems and content for a global enterprise.  Satellite 6 covers the customer requested satellite 5 use cases, but it also includes functionality that enables larger scale, federation of content, better control of systems during the provisioning process and a truly simplified approach to life cycle management. Also evolved in satellite 6 is the the inherent approach to ceritifcate based entitlements and integrated subscription management. Satellite 6 is based on years of customer feedback and is an evolution of previous versions.
>
>
>2.0
>
>I also included a few suggestions below for the table in chapter 2.  I also added a one liner after each providing a more context.
>
>Comparison of Satellite 5 and 6
>
>Open Source Projects, A single project called spacewalk vs modular project approach (katello, foreman, puppet, pulp and candlepin
>The development approach to creating the enterprise satellite platform.
>
>Subscription Types, pool or channel based  vs. certificate-based
>Subscription management improved over the years from a pool or channel based approach to a more specific certificate based approach.  Certificate-based subscription management provides better overall control of subscriptions of those consuming clients.
>
>Subscription Methods or Satellite Subscription Consumption
>This is the way in which satellite is enabled to sync and distribute Red Hat content.
>
>Organizational Approach, Multi-Org vs Multi-Org and Multi-Location
>Both satellite 5 and 6 have a concept of multi-org, but satellite 6 also includes functionality to include context of of the location.
>
>Software and Configuration Content, distributed via channels vs distributed via content view published and promoted through environments 
>
>* In satellite 6 a content view contains a chosen set of software repositories and configuration modules that are published and promoted to an environment. Client systems consume its software and configurations through its environment associations.
>
>I also had a few suggestions in the glossary section.
>
>Glossary of Terms...
>
>Content View, I do not believe you need a comma after 'modules' 
>
>External Node Classifier, might be worth noting that the capsules act as the puppet masters in satellite 6 deployment
>
>Product, might be worth noting that products can be Red Hat products and newly created products and made up of software and configuration content.
>
>Promote, The act of moving a content view comprised of software and configuration content from on app life cycle environment to another such as moving from development to qa to production.
>
>Provisioning Template, I believe you meant to say satellite 5 instead 6 at the endHi David/Athene, I am on the sat-sme team, and I was going to work on a comparison guide between satellite 5 and 6 for SAs.  I found your transition guide, which I thought looks great. I was reviewing the doc, and I made a few suggestions below.  Please feel welcome to use if you think they are relevant.
>
>For the beginning satellite 5 and satellite 6 intros in chapter 1.
>
>1.1
>
>Red Hat Satellite 5 is life cycle management tool that includes the capabilities to deploy, manage and monitor a large number of systems.  Satellite 5 can be set-up in a connected or disconnected mode in which Red Hat software is distributed to client systems using the original pooled subscription approach. The pooled subscription concept is similar to the way in which clients consume entitlements from the classic Red Hat Network.  For more information on classic Red Hat Network, see the following link "" 
>
>The popular functionality of satellite 5 included the ability to provision a large number of systems utilizing a kickstart files and activation keys to install and configure systems to a predictable state. This provisioning process associated systems to a designated organizations, software and configuration channels as well as placed systems within predefined systems group and or groups.  The Satellite 5 provisioning functionality enabled administrators to provision thousands of systems in a consistent manner.
>
>Once systems are provisioned another popular functionality is the ability to manage software and configuration files across large numbers of systems in local or remote environments.  One of the really well understood concepts of managing software and configuration files in satellite 5 is the concept of channels. All software and configurations are managed and distributed through channels, and any client needing access to software or configuration content would need to be associated to the one or many relevant channels.  Additionally, channel cloning capability enabled admins to create the much needed development-production environments required by most enterprises. 
>
>While satellite 5 is well know for providing a solid platform for managing software and configurations files for a large number of systems and also well known for the simplicity and consistency of the provisioning process, the satellite 5 systems management platform is also well known for delivering the correct versions and updated versions of content to the correct systems in a very structured manner. Administrators managed the satellite and systems management processes through the satellite webui and also satellite api interfaces.
>
>1.2 
>
>Red Hat Satellite 6 is the evolution of Red Hat's life cycle management platform.  It provides the capabilities that administrators have come to expect in a tool focused on managing systems and content for a global enterprise.  Satellite 6 covers the customer requested satellite 5 use cases, but it also includes functionality that enables larger scale, federation of content, better control of systems during the provisioning process and a truly simplified approach to life cycle management. Also evolved in satellite 6 is the the inherent approach to ceritifcate based entitlements and integrated subscription management. Satellite 6 is based on years of customer feedback and is an evolution of previous versions.
>
>
>2.0
>
>I also included a few suggestions below for the table in chapter 2.  I also added a one liner after each providing a more context.
>
>Comparison of Satellite 5 and 6
>
>Open Source Projects, A single project called spacewalk vs modular project approach (katello, foreman, puppet, pulp and candlepin
>The development approach to creating the enterprise satellite platform.
>
>Subscription Types, pool or channel based  vs. certificate-based
>Subscription management improved over the years from a pool or channel based approach to a more specific certificate based approach.  Certificate-based subscription management provides better overall control of subscriptions of those consuming clients.
>
>Subscription Methods or Satellite Subscription Consumption
>This is the way in which satellite is enabled to sync and distribute Red Hat content.
>
>Organizational Approach, Multi-Org vs Multi-Org and Multi-Location
>Both satellite 5 and 6 have a concept of multi-org, but satellite 6 also includes functionality to include context of of the location.
>
>Software and Configuration Content, distributed via channels vs distributed via content view published and promoted through environments 
>
>* In satellite 6 a content view contains a chosen set of software repositories and configuration modules that are published and promoted to an environment. Client systems consume its software and configurations through its environment associations.
>
>I also had a few suggestions in the glossary section.
>
>Glossary of Terms...
>
>Content View, I do not believe you need a comma after 'modules' 
>
>External Node Classifier, might be worth noting that the capsules act as the puppet masters in satellite 6 deployment
>
>Product, might be worth noting that products can be Red Hat products and newly created products and made up of software and configuration content.
>
>Promote, The act of moving a content view comprised of software and configuration content from on app life cycle environment to another such as moving from development to qa to production.
>
>Provisioning Template, I believe you meant to say satellite 5 instead 6 at the end

Actions: View

Attachments on bug 1121816: 919782