[Starlingx-discuss] Restructuring round 2
Story: https://storyboard.openstack.org/#!/story/2002801 *Goals:* 1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils 2) Restructure the directories under which packages are to be found. Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up. Directories should descriptive of the class of packages to be found within. Intent is to preserve update history as best is is possible. *Timeline: * Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed. *Code Reviews: * Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review? *Details of directories/groups ...* Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support *Details of packages ...* Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog ceph/ python-cephclient config/ e2fsprogs facter nfs-utils nfscheck puppet-4.8.2 puppet-modules kernel/ kernel-std kernel-rt kernel/kernel-modules/ mlnx-ofa_kernel ldap/ nss-pam-ldapd openldap logging/ syslog-ng logrotate networking/ lldpd iproute mellanox python-ryu mlx4-config python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm security/ shim-signed shim-unsigned tboot strorage-drivers/ python-3parclient python-lefthandclient virt/ cloud-init libvirt libvirt-python qemu tools/ storage-topology vm-topology utilities/ tis-extensions namespace-utils nova-utils update-motd Relocated packages (stx-utils to stx-update): enable-dev-patch Relocated packages (stx-utils to stx-integ): config-files/ io-scheduler filesystem/ filesystem-scripts grub/ grubby logging/ logmgmt tools/ collector monitor-tools tools/engtools/ hostdata-collectors parsers utilities/ build-info branding (formerly wrs-branding) platform-util Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm database/ mariadb filesystem/ iscsi-initiator-utils filesystem/drbd/ drbd-tools kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd ldap/ ldapscripts networking/ iptables net-tools Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync database/ python-psycopg2 filesystem/ parted grub/ grub2 security/ python-keyring Delete two packages from stx-integ: tgt irqbalance Delete two packages from stx-gplv3: seabios sysvinit Delete one package from stx-utils: io-monitor
Hi Scott, Thanks for the info. There's something I would like to bring into the discussion of the consolidation. It has started a discussion on what infrastructure we need to have a CI of StarlingX and an evaluation on OBS (openbuildservice) and Koji has started. Taking that in mind I'm wondering how this consolidation can help/affect to adapt the StarlingX building Into one of these infrastructures, as far as I recall, both solutions requires to have a repository per rpm. What are your thoughts on this? Thanks -Erich From: Scott Little <scott.little@windriver.com> Date: Tuesday, July 17, 2018 at 10:08 AM To: "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] Restructuring round 2 Story: https://storyboard.openstack.org/#!/story/2002801 Goals: 1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils 2) Restructure the directories under which packages are to be found. Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up. Directories should descriptive of the class of packages to be found within. Intent is to preserve update history as best is is possible. Timeline: Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed. Code Reviews: Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review? Details of directories/groups ... Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support Details of packages ... Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog ceph/ python-cephclient config/ e2fsprogs facter nfs-utils nfscheck puppet-4.8.2 puppet-modules kernel/ kernel-std kernel-rt kernel/kernel-modules/ mlnx-ofa_kernel ldap/ nss-pam-ldapd openldap logging/ syslog-ng logrotate networking/ lldpd iproute mellanox python-ryu mlx4-config python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm security/ shim-signed shim-unsigned tboot strorage-drivers/ python-3parclient python-lefthandclient virt/ cloud-init libvirt libvirt-python qemu tools/ storage-topology vm-topology utilities/ tis-extensions namespace-utils nova-utils update-motd Relocated packages (stx-utils to stx-update): enable-dev-patch Relocated packages (stx-utils to stx-integ): config-files/ io-scheduler filesystem/ filesystem-scripts grub/ grubby logging/ logmgmt tools/ collector monitor-tools tools/engtools/ hostdata-collectors parsers utilities/ build-info branding (formerly wrs-branding) platform-util Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm database/ mariadb filesystem/ iscsi-initiator-utils filesystem/drbd/ drbd-tools kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd ldap/ ldapscripts networking/ iptables net-tools Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync database/ python-psycopg2 filesystem/ parted grub/ grub2 security/ python-keyring Delete two packages from stx-integ: tgt irqbalance Delete two packages from stx-gplv3: seabios sysvinit Delete one package from stx-utils: io-monitor
I think the build system alternatives question is independent of this initiative and probably does not impact +/-. Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran@intel.com] Sent: Tuesday, July 17, 2018 11:54 AM To: Little, Scott <Scott.Little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Restructuring round 2 Hi Scott, Thanks for the info. There's something I would like to bring into the discussion of the consolidation. It has started a discussion on what infrastructure we need to have a CI of StarlingX and an evaluation on OBS (openbuildservice) and Koji has started. Taking that in mind I'm wondering how this consolidation can help/affect to adapt the StarlingX building Into one of these infrastructures, as far as I recall, both solutions requires to have a repository per rpm. What are your thoughts on this? Thanks -Erich From: Scott Little <scott.little@windriver.com> Date: Tuesday, July 17, 2018 at 10:08 AM To: "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] Restructuring round 2 Story: https://storyboard.openstack.org/#!/story/2002801 Goals: 1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils 2) Restructure the directories under which packages are to be found. Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up. Directories should descriptive of the class of packages to be found within. Intent is to preserve update history as best is is possible. Timeline: Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed. Code Reviews: Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review? Details of directories/groups ... Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support Details of packages ... Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog ceph/ python-cephclient config/ e2fsprogs facter nfs-utils nfscheck puppet-4.8.2 puppet-modules kernel/ kernel-std kernel-rt kernel/kernel-modules/ mlnx-ofa_kernel ldap/ nss-pam-ldapd openldap logging/ syslog-ng logrotate networking/ lldpd iproute mellanox python-ryu mlx4-config python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm security/ shim-signed shim-unsigned tboot strorage-drivers/ python-3parclient python-lefthandclient virt/ cloud-init libvirt libvirt-python qemu tools/ storage-topology vm-topology utilities/ tis-extensions namespace-utils nova-utils update-motd Relocated packages (stx-utils to stx-update): enable-dev-patch Relocated packages (stx-utils to stx-integ): config-files/ io-scheduler filesystem/ filesystem-scripts grub/ grubby logging/ logmgmt tools/ collector monitor-tools tools/engtools/ hostdata-collectors parsers utilities/ build-info branding (formerly wrs-branding) platform-util Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm database/ mariadb filesystem/ iscsi-initiator-utils filesystem/drbd/ drbd-tools kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd ldap/ ldapscripts networking/ iptables net-tools Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync database/ python-psycopg2 filesystem/ parted grub/ grub2 security/ python-keyring Delete two packages from stx-integ: tgt irqbalance Delete two packages from stx-gplv3: seabios sysvinit Delete one package from stx-utils: io-monitor _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Important subjects that I want to participate in, but I think that's a subject for a different thread. Long term solutions, versus a short term need to get WindRiver converged onto StarlingX. For now, we'd like to get a rational directory structure. Subdivision of current gits into per-package gits can happen later if that's the path we choose. Scott On 18-07-17 11:54 AM, Cordoba Malibran, Erich wrote:
Hi Scott,
Thanks for the info. There's something I would like to bring into the discussion of the consolidation. It has started a discussion on what infrastructure we need to have a CI of StarlingX and an evaluation on OBS (openbuildservice) and Koji has started.
Taking that in mind I'm wondering how this consolidation can help/affect to adapt the StarlingX building Into one of these infrastructures, as far as I recall, both solutions requires to have a repository per rpm.
What are your thoughts on this?
Thanks
-Erich
Agree, we can move that into a later discussion. Taking back into the topic I think that the proposal needs a section describing why this is needed or what is the problem that we are trying to solve with these changes. -Erich On 7/17/18, 11:16 AM, "Scott Little" <scott.little@windriver.com> wrote: Important subjects that I want to participate in, but I think that's a subject for a different thread. Long term solutions, versus a short term need to get WindRiver converged onto StarlingX. For now, we'd like to get a rational directory structure. Subdivision of current gits into per-package gits can happen later if that's the path we choose. Scott On 18-07-17 11:54 AM, Cordoba Malibran, Erich wrote: > Hi Scott, > > Thanks for the info. There's something I would like to bring into the discussion of the consolidation. > It has started a discussion on what infrastructure we need to have a CI of StarlingX and an evaluation on > OBS (openbuildservice) and Koji has started. > > Taking that in mind I'm wondering how this consolidation can help/affect to adapt the StarlingX building > Into one of these infrastructures, as far as I recall, both solutions requires to have a repository per rpm. > > What are your thoughts on this? > > Thanks > > -Erich
This was posted to the mailing list over a week ago. Brent -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran@intel.com] Sent: Tuesday, July 17, 2018 12:32 PM To: Little, Scott <Scott.Little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Restructuring round 2 Agree, we can move that into a later discussion. Taking back into the topic I think that the proposal needs a section describing why this is needed or what is the problem that we are trying to solve with these changes. -Erich On 7/17/18, 11:16 AM, "Scott Little" <scott.little@windriver.com> wrote: Important subjects that I want to participate in, but I think that's a subject for a different thread. Long term solutions, versus a short term need to get WindRiver converged onto StarlingX. For now, we'd like to get a rational directory structure. Subdivision of current gits into per-package gits can happen later if that's the path we choose. Scott On 18-07-17 11:54 AM, Cordoba Malibran, Erich wrote: > Hi Scott, > > Thanks for the info. There's something I would like to bring into the discussion of the consolidation. > It has started a discussion on what infrastructure we need to have a CI of StarlingX and an evaluation on > OBS (openbuildservice) and Koji has started. > > Taking that in mind I'm wondering how this consolidation can help/affect to adapt the StarlingX building > Into one of these infrastructures, as far as I recall, both solutions requires to have a repository per rpm. > > What are your thoughts on this? > > Thanks > > -Erich _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Scott, Thanks for getting started on this. As you may know I worked on the Yocto Project and worked on the initial split that you mention came from WRLinux. I think you have done a good job with the reorganization. As I am just coming up to speed I might have a couple of dumb questions to as ask I don't know of all the content changes yet (Patches, config changes, ...). A simple high level question, would it make sense to segregate out everything that is CentOS into base? That way as we move to more of an OS independent setup, the core directory could possibly go away? Can you add some definition as the what belongs in some of the other directories (config vs config-files, tools vs utilities)? See more direct questions inline in the lists below. Do you have a full "after" list, that might help then just seeing what's being relocated. Thanks Sau! On 07/17/2018 08:07 AM, Scott Little wrote:
Story: https://storyboard.openstack.org/#!/story/2002801
*Goals:*
1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils
2) Restructure the directories under which packages are to be found.
Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up.
Directories should descriptive of the class of packages to be found within.
Intent is to preserve update history as best is is possible.
*Timeline: *
Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed.
*Code Reviews: *
Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review?
*Details of directories/groups ...*
Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt
Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security
Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support
*Details of packages ...*
Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog
ceph/ python-cephclient
config/ e2fsprogs Why e2fsprogs in config vs base?
facter nfs-utils Same here base? nfscheck puppet-4.8.2 puppet-modules
kernel/ kernel-std kernel-rt
kernel/kernel-modules/ mlnx-ofa_kernel
ldap/ nss-pam-ldapd openldap
logging/ syslog-ng logrotate With just 2 items maybe base as they are part of CentOS?
networking/ lldpd iproute
I could see this one both ways it's one item that could be part of base.
mellanox python-ryu mlx4-config
python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm
security/ shim-signed shim-unsigned tboot
strorage-drivers/ python-3parclient python-lefthandclient
virt/ cloud-init libvirt libvirt-python qemu
tools/ storage-topology vm-topology
utilities/ tis-extensions namespace-utils nova-utils update-motd
Relocated packages (stx-utils to stx-update): enable-dev-patch
Relocated packages (stx-utils to stx-integ):
config-files/ io-scheduler
filesystem/ filesystem-scripts
grub/ grubby
logging/ logmgmt
tools/ collector monitor-tools
tools/engtools/ hostdata-collectors parsers
utilities/ build-info branding (formerly wrs-branding) platform-util
Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm
database/ mariadb
filesystem/ iscsi-initiator-utils
filesystem/drbd/ drbd-tools
kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd
ldap/ ldapscripts
networking/ iptables net-tools
Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync
database/ python-psycopg2
filesystem/ parted
grub/ grub2
security/ python-keyring
Delete two packages from stx-integ: tgt irqbalance
Delete two packages from stx-gplv3: seabios sysvinit
Delete one package from stx-utils: io-monitor
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
I think this proposal makes sense. As we get patches merged to their upstreams, we can replace much of this with upstream binaries and over time remove much of this content. brucej -----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Tuesday, July 17, 2018 9:38 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Restructuring round 2 Scott, Thanks for getting started on this. As you may know I worked on the Yocto Project and worked on the initial split that you mention came from WRLinux. I think you have done a good job with the reorganization. As I am just coming up to speed I might have a couple of dumb questions to as ask I don't know of all the content changes yet (Patches, config changes, ...). A simple high level question, would it make sense to segregate out everything that is CentOS into base? That way as we move to more of an OS independent setup, the core directory could possibly go away? Can you add some definition as the what belongs in some of the other directories (config vs config-files, tools vs utilities)? See more direct questions inline in the lists below. Do you have a full "after" list, that might help then just seeing what's being relocated. Thanks Sau! On 07/17/2018 08:07 AM, Scott Little wrote:
Story: https://storyboard.openstack.org/#!/story/2002801
*Goals:*
1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils
2) Restructure the directories under which packages are to be found.
Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up.
Directories should descriptive of the class of packages to be found within.
Intent is to preserve update history as best is is possible.
*Timeline: *
Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed.
*Code Reviews: *
Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review?
*Details of directories/groups ...*
Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt
Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security
Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support
*Details of packages ...*
Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog
ceph/ python-cephclient
config/ e2fsprogs Why e2fsprogs in config vs base?
facter nfs-utils Same here base? nfscheck puppet-4.8.2 puppet-modules
kernel/ kernel-std kernel-rt
kernel/kernel-modules/ mlnx-ofa_kernel
ldap/ nss-pam-ldapd openldap
logging/ syslog-ng logrotate With just 2 items maybe base as they are part of CentOS?
networking/ lldpd iproute
I could see this one both ways it's one item that could be part of base.
mellanox python-ryu mlx4-config
python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm
security/ shim-signed shim-unsigned tboot
strorage-drivers/ python-3parclient python-lefthandclient
virt/ cloud-init libvirt libvirt-python qemu
tools/ storage-topology vm-topology
utilities/ tis-extensions namespace-utils nova-utils update-motd
Relocated packages (stx-utils to stx-update): enable-dev-patch
Relocated packages (stx-utils to stx-integ):
config-files/ io-scheduler
filesystem/ filesystem-scripts
grub/ grubby
logging/ logmgmt
tools/ collector monitor-tools
tools/engtools/ hostdata-collectors parsers
utilities/ build-info branding (formerly wrs-branding) platform-util
Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm
database/ mariadb
filesystem/ iscsi-initiator-utils
filesystem/drbd/ drbd-tools
kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd
ldap/ ldapscripts
networking/ iptables net-tools
Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync
database/ python-psycopg2
filesystem/ parted
grub/ grub2
security/ python-keyring
Delete two packages from stx-integ: tgt irqbalance
Delete two packages from stx-gplv3: seabios sysvinit
Delete one package from stx-utils: io-monitor
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On 18-07-17 12:38 PM, Saul Wold wrote:
Scott,
Thanks for getting started on this. As you may know I worked on the Yocto Project and worked on the initial split that you mention came from WRLinux.
I think you have done a good job with the reorganization. As I am just coming up to speed I might have a couple of dumb questions to as ask I don't know of all the content changes yet (Patches, config changes, ...).
A simple high level question, would it make sense to segregate out everything that is CentOS into base? That way as we move to more of an OS independent setup, the core directory could possibly go away?
[SL] We were envisioning function rather than upstream source as the reason for the categories. 'Base' are those packages that are pretty much universal to a Linux server.
Can you add some definition as the what belongs in some of the other directories (config vs config-files, tools vs utilities)?
[SL] Tools vs utilities. Not clear I'll admit. Utilities are small, special purpose, shortcuts that could otherwise be accomplished by the right set of CLI commands. Tools are bigger, more complex, e.g. investigating and analyze the state of the system.
See more direct questions inline in the lists below.
Do you have a full "after" list, that might help then just seeing what's being relocated.
[SL] will send seperately
Thanks Sau!
On 07/17/2018 08:07 AM, Scott Little wrote:
Story: https://storyboard.openstack.org/#!/story/2002801
*Goals:*
1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils
2) Restructure the directories under which packages are to be found.
Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up.
Directories should descriptive of the class of packages to be found within.
Intent is to preserve update history as best is is possible.
*Timeline: *
Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed.
*Code Reviews: *
Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review?
*Details of directories/groups ...*
Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt
Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security
Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support
*Details of packages ...*
Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog
ceph/ python-cephclient
config/ e2fsprogs Why e2fsprogs in config vs base?
[SL] error on my part. Some sort of cut-n-paste error. config/ facter puppet-4.8.2 puppet-modules filesystem/ e2fsprogs nfs-utils nfscheck
facter nfs-utils Same here base? nfscheck puppet-4.8.2 puppet-modules
kernel/ kernel-std kernel-rt
kernel/kernel-modules/ mlnx-ofa_kernel
ldap/ nss-pam-ldapd openldap
logging/ syslog-ng logrotate With just 2 items maybe base as they are part of CentOS?
[SL] additional packages might land here that filter/manipulate/look for trends in logs
networking/ lldpd iproute
I could see this one both ways it's one item that could be part of base.
mellanox python-ryu mlx4-config
python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm
security/ shim-signed shim-unsigned tboot
strorage-drivers/ python-3parclient python-lefthandclient
virt/ cloud-init libvirt libvirt-python qemu
tools/ storage-topology vm-topology
utilities/ tis-extensions namespace-utils nova-utils update-motd
Relocated packages (stx-utils to stx-update): enable-dev-patch
Relocated packages (stx-utils to stx-integ):
config-files/ io-scheduler
filesystem/ filesystem-scripts
grub/ grubby
logging/ logmgmt
tools/ collector monitor-tools
tools/engtools/ hostdata-collectors parsers
utilities/ build-info branding (formerly wrs-branding) platform-util
Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm
database/ mariadb
filesystem/ iscsi-initiator-utils
filesystem/drbd/ drbd-tools
kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd
ldap/ ldapscripts
networking/ iptables net-tools
Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync
database/ python-psycopg2
filesystem/ parted
grub/ grub2
security/ python-keyring
Delete two packages from stx-integ: tgt irqbalance
Delete two packages from stx-gplv3: seabios sysvinit
Delete one package from stx-utils: io-monitor
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
The full list of packages in stx-integ after proposed changes On 18-07-17 03:10 PM, Scott Little wrote:
On 18-07-17 12:38 PM, Saul Wold wrote:
Do you have a full "after" list, that might help then just seeing what's being relocated.
[SL] will send seperately
base/anaconda base/bash base/centos-release base/cgcs-users base/cluster-resource-agents base/crontabs base/dhcp base/dnsmasq base/dpkg base/haproxy base/initscripts base/libevent base/libfdt base/lighttpd base/lshell base/memcached base/netpbm base/net-snmp base/novnc base/ntp base/openssh base/pam base/rpm base/rsync base/sanlock base/setup base/shadow-utils base/sudo base/systemd base/util-linux base/vim base/watchdog ceph/python-cephclient config/facter config/puppet-4.8.2 config/puppet-modules/openstack/puppet-ceilometer-11.3.0 config/puppet-modules/openstack/puppet-ceph-2.2.0 config/puppet-modules/openstack/puppet-cinder-11.3.0 config/puppet-modules/openstack/puppet-glance-11.3.0 config/puppet-modules/openstack/puppet-heat-11.3.0 config/puppet-modules/openstack/puppet-horizon-9.5.0 config/puppet-modules/openstack/puppet-ironic-11.3.0 config/puppet-modules/openstack/puppet-keystone-11.3.0 config/puppet-modules/openstack/puppet-magnum-11.3.0 config/puppet-modules/openstack/puppet-memcached-3.0.2 config/puppet-modules/openstack/puppet-murano-11.3.0 config/puppet-modules/openstack/puppet-neutron-11.3.0 config/puppet-modules/openstack/puppet-nova-11.4.0 config/puppet-modules/openstack/puppet-openstacklib-11.3.0 config/puppet-modules/openstack/puppet-oslo-11.3.0 config/puppet-modules/openstack/puppet-panko-11.3.0 config/puppet-modules/openstack/puppet-swift-11.3.0 config/puppet-modules/puppet-boolean-1.0.2 config/puppet-modules/puppet-create_resources config/puppet-modules/puppet-dnsmasq config/puppet-modules/puppet-drbd-0.3.1 config/puppet-modules/puppet-filemapper config/puppet-modules/puppet-haproxy-1.5.0 config/puppet-modules/puppet-ldap config/puppet-modules/puppet-lvm config/puppet-modules/puppet-network config/puppet-modules/puppet-nslcd config/puppet-modules/puppet-postgresql-4.8.0 config/puppet-modules/puppet-puppi config/puppet-modules/puppet-rabbitmq-5.5.0 config/puppet-modules/puppet-staging config/puppet-modules/puppet-stdlib-4.12.0 config-files/io-scheduler database/mariadb database/python-psycopg2 filesystem/drbd/drbd-tools filesystem/e2fsprogs filesystem/filesystem-scripts filesystem/iscsi-initiator-utils filesystem/nfscheck filesystem/nfs-utils filesystem/parted grub/grub2 grub/grubby kernel/kernel-rt kernel/kernel-std kernel/kernel-modules/drbd kernel/kernel-modules/integrity kernel/kernel-modules/intel-e1000e kernel/kernel-modules/intel-i40e kernel/kernel-modules/intel-i40evf kernel/kernel-modules/intel-ixgbe kernel/kernel-modules/intel-ixgbevf kernel/kernel-modules/mlnx-ofa_kernel kernel/kernel-modules/qat17 kernel/kernel-modules/tpmdd kubernetes/docker-ce kubernetes/kubernetes ldap/ldapscripts ldap/nss-pam-ldapd ldap/openldap logging/logmgmt logging/logrotate logging/syslog-ng monitoring/collectd-extensions monitoring/influxdb-extensions networking/iproute networking/iptables networking/lldpd networking/mellanox/libibverbs networking/mellanox/libmlx4 networking/mellanox/libmlx5 networking/mellanox/mlx4-config networking/mellanox/rdma-core networking/net-tools networking/openvswitch networking/python-ryu networking/scapy python/python-2.7.5 python/python-django python/python-eventlet python/python-gunicorn python/python-requests python/python-setuptools python/python-smartpm restapi-doc security/audit security/libtpms security/python-keyring security/shim-signed security/shim-unsigned security/spectre-meltdown-checker security/swtpm security/tboot security/tpm2-openssl-engine security/tpm2-tools security/tss2 security/wrs-ssl strorage-drivers/python-3parclient strorage-drivers/python-lefthandclient tools/collector tools/engtools/hostdata-collectors tools/monitor-tools tools/vm-topology utilities/branding utilities/build-info utilities/namespace-utils utilities/nova-utils utilities/platform-util utilities/tis-extensions utilities/update-motd virt/cloud-init virt/libvirt virt/libvirt-python virt/qemu
On 07/17/2018 12:25 PM, Scott Little wrote:
The full list of packages in stx-integ after proposed changes
Thanks, this help me understand some of the context and content in the re-arranged packages. I understand your thought of functionality over upstream source, but it would make it clearer, especially for the OS upstream bits to all be contained in "base". That way we work so reduce that one directory to zero. I am not going to block, just saying. I am currently pursuing the existing stx tree trying to understand some of the changes. I will send email on those later. Sau!
On 18-07-17 03:10 PM, Scott Little wrote:
On 18-07-17 12:38 PM, Saul Wold wrote:
Do you have a full "after" list, that might help then just seeing what's being relocated.
[SL] will send seperately
base/anaconda base/bash base/centos-release base/cgcs-users base/cluster-resource-agents base/crontabs base/dhcp base/dnsmasq base/dpkg base/haproxy base/initscripts base/libevent base/libfdt base/lighttpd base/lshell base/memcached base/netpbm base/net-snmp base/novnc base/ntp base/openssh base/pam base/rpm base/rsync base/sanlock base/setup base/shadow-utils base/sudo base/systemd base/util-linux base/vim base/watchdog
ceph/python-cephclient
config/facter config/puppet-4.8.2 config/puppet-modules/openstack/puppet-ceilometer-11.3.0 config/puppet-modules/openstack/puppet-ceph-2.2.0 config/puppet-modules/openstack/puppet-cinder-11.3.0 config/puppet-modules/openstack/puppet-glance-11.3.0 config/puppet-modules/openstack/puppet-heat-11.3.0 config/puppet-modules/openstack/puppet-horizon-9.5.0 config/puppet-modules/openstack/puppet-ironic-11.3.0 config/puppet-modules/openstack/puppet-keystone-11.3.0 config/puppet-modules/openstack/puppet-magnum-11.3.0 config/puppet-modules/openstack/puppet-memcached-3.0.2 config/puppet-modules/openstack/puppet-murano-11.3.0 config/puppet-modules/openstack/puppet-neutron-11.3.0 config/puppet-modules/openstack/puppet-nova-11.4.0 config/puppet-modules/openstack/puppet-openstacklib-11.3.0 config/puppet-modules/openstack/puppet-oslo-11.3.0 config/puppet-modules/openstack/puppet-panko-11.3.0 config/puppet-modules/openstack/puppet-swift-11.3.0 config/puppet-modules/puppet-boolean-1.0.2 config/puppet-modules/puppet-create_resources config/puppet-modules/puppet-dnsmasq config/puppet-modules/puppet-drbd-0.3.1 config/puppet-modules/puppet-filemapper config/puppet-modules/puppet-haproxy-1.5.0 config/puppet-modules/puppet-ldap config/puppet-modules/puppet-lvm config/puppet-modules/puppet-network config/puppet-modules/puppet-nslcd config/puppet-modules/puppet-postgresql-4.8.0 config/puppet-modules/puppet-puppi config/puppet-modules/puppet-rabbitmq-5.5.0 config/puppet-modules/puppet-staging config/puppet-modules/puppet-stdlib-4.12.0
config-files/io-scheduler
database/mariadb database/python-psycopg2
filesystem/drbd/drbd-tools filesystem/e2fsprogs filesystem/filesystem-scripts filesystem/iscsi-initiator-utils filesystem/nfscheck filesystem/nfs-utils filesystem/parted
grub/grub2 grub/grubby
kernel/kernel-rt kernel/kernel-std
kernel/kernel-modules/drbd kernel/kernel-modules/integrity kernel/kernel-modules/intel-e1000e kernel/kernel-modules/intel-i40e kernel/kernel-modules/intel-i40evf kernel/kernel-modules/intel-ixgbe kernel/kernel-modules/intel-ixgbevf kernel/kernel-modules/mlnx-ofa_kernel kernel/kernel-modules/qat17 kernel/kernel-modules/tpmdd
kubernetes/docker-ce kubernetes/kubernetes
ldap/ldapscripts ldap/nss-pam-ldapd ldap/openldap
logging/logmgmt logging/logrotate logging/syslog-ng
monitoring/collectd-extensions monitoring/influxdb-extensions
networking/iproute networking/iptables networking/lldpd networking/mellanox/libibverbs networking/mellanox/libmlx4 networking/mellanox/libmlx5 networking/mellanox/mlx4-config networking/mellanox/rdma-core networking/net-tools networking/openvswitch networking/python-ryu networking/scapy
python/python-2.7.5 python/python-django python/python-eventlet python/python-gunicorn python/python-requests python/python-setuptools python/python-smartpm
restapi-doc
security/audit security/libtpms security/python-keyring security/shim-signed security/shim-unsigned security/spectre-meltdown-checker security/swtpm security/tboot security/tpm2-openssl-engine security/tpm2-tools security/tss2 security/wrs-ssl
strorage-drivers/python-3parclient strorage-drivers/python-lefthandclient
tools/collector tools/engtools/hostdata-collectors tools/monitor-tools tools/vm-topology
utilities/branding utilities/build-info utilities/namespace-utils utilities/nova-utils utilities/platform-util utilities/tis-extensions utilities/update-motd
virt/cloud-init virt/libvirt virt/libvirt-python virt/qemu
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
You also need to consider the designer workflow including the number of repos they have to change to develop features. For instance having klms and the kernel spread across multiple repos makes no sense. Brent -----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Tuesday, July 17, 2018 3:56 PM To: Little, Scott <Scott.Little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Restructuring round 2 On 07/17/2018 12:25 PM, Scott Little wrote:
The full list of packages in stx-integ after proposed changes
Thanks, this help me understand some of the context and content in the re-arranged packages. I understand your thought of functionality over upstream source, but it would make it clearer, especially for the OS upstream bits to all be contained in "base". That way we work so reduce that one directory to zero. I am not going to block, just saying. I am currently pursuing the existing stx tree trying to understand some of the changes. I will send email on those later. Sau!
On 18-07-17 03:10 PM, Scott Little wrote:
On 18-07-17 12:38 PM, Saul Wold wrote:
Do you have a full "after" list, that might help then just seeing what's being relocated.
[SL] will send seperately
base/anaconda base/bash base/centos-release base/cgcs-users base/cluster-resource-agents base/crontabs base/dhcp base/dnsmasq base/dpkg base/haproxy base/initscripts base/libevent base/libfdt base/lighttpd base/lshell base/memcached base/netpbm base/net-snmp base/novnc base/ntp base/openssh base/pam base/rpm base/rsync base/sanlock base/setup base/shadow-utils base/sudo base/systemd base/util-linux base/vim base/watchdog
ceph/python-cephclient
config/facter config/puppet-4.8.2 config/puppet-modules/openstack/puppet-ceilometer-11.3.0 config/puppet-modules/openstack/puppet-ceph-2.2.0 config/puppet-modules/openstack/puppet-cinder-11.3.0 config/puppet-modules/openstack/puppet-glance-11.3.0 config/puppet-modules/openstack/puppet-heat-11.3.0 config/puppet-modules/openstack/puppet-horizon-9.5.0 config/puppet-modules/openstack/puppet-ironic-11.3.0 config/puppet-modules/openstack/puppet-keystone-11.3.0 config/puppet-modules/openstack/puppet-magnum-11.3.0 config/puppet-modules/openstack/puppet-memcached-3.0.2 config/puppet-modules/openstack/puppet-murano-11.3.0 config/puppet-modules/openstack/puppet-neutron-11.3.0 config/puppet-modules/openstack/puppet-nova-11.4.0 config/puppet-modules/openstack/puppet-openstacklib-11.3.0 config/puppet-modules/openstack/puppet-oslo-11.3.0 config/puppet-modules/openstack/puppet-panko-11.3.0 config/puppet-modules/openstack/puppet-swift-11.3.0 config/puppet-modules/puppet-boolean-1.0.2 config/puppet-modules/puppet-create_resources config/puppet-modules/puppet-dnsmasq config/puppet-modules/puppet-drbd-0.3.1 config/puppet-modules/puppet-filemapper config/puppet-modules/puppet-haproxy-1.5.0 config/puppet-modules/puppet-ldap config/puppet-modules/puppet-lvm config/puppet-modules/puppet-network config/puppet-modules/puppet-nslcd config/puppet-modules/puppet-postgresql-4.8.0 config/puppet-modules/puppet-puppi config/puppet-modules/puppet-rabbitmq-5.5.0 config/puppet-modules/puppet-staging config/puppet-modules/puppet-stdlib-4.12.0
config-files/io-scheduler
database/mariadb database/python-psycopg2
filesystem/drbd/drbd-tools filesystem/e2fsprogs filesystem/filesystem-scripts filesystem/iscsi-initiator-utils filesystem/nfscheck filesystem/nfs-utils filesystem/parted
grub/grub2 grub/grubby
kernel/kernel-rt kernel/kernel-std
kernel/kernel-modules/drbd kernel/kernel-modules/integrity kernel/kernel-modules/intel-e1000e kernel/kernel-modules/intel-i40e kernel/kernel-modules/intel-i40evf kernel/kernel-modules/intel-ixgbe kernel/kernel-modules/intel-ixgbevf kernel/kernel-modules/mlnx-ofa_kernel kernel/kernel-modules/qat17 kernel/kernel-modules/tpmdd
kubernetes/docker-ce kubernetes/kubernetes
ldap/ldapscripts ldap/nss-pam-ldapd ldap/openldap
logging/logmgmt logging/logrotate logging/syslog-ng
monitoring/collectd-extensions monitoring/influxdb-extensions
networking/iproute networking/iptables networking/lldpd networking/mellanox/libibverbs networking/mellanox/libmlx4 networking/mellanox/libmlx5 networking/mellanox/mlx4-config networking/mellanox/rdma-core networking/net-tools networking/openvswitch networking/python-ryu networking/scapy
python/python-2.7.5 python/python-django python/python-eventlet python/python-gunicorn python/python-requests python/python-setuptools python/python-smartpm
restapi-doc
security/audit security/libtpms security/python-keyring security/shim-signed security/shim-unsigned security/spectre-meltdown-checker security/swtpm security/tboot security/tpm2-openssl-engine security/tpm2-tools security/tss2 security/wrs-ssl
strorage-drivers/python-3parclient strorage-drivers/python-lefthandclient
tools/collector tools/engtools/hostdata-collectors tools/monitor-tools tools/vm-topology
utilities/branding utilities/build-info utilities/namespace-utils utilities/nova-utils utilities/platform-util utilities/tis-extensions utilities/update-motd
virt/cloud-init virt/libvirt virt/libvirt-python virt/qemu
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
If we are talking centos + epel, the packages that need upstreaming can be quickly identified by looking for 'mirror:' in centos/srpm_path grep 'mirror:' $(find . -path '*/centos/srpm_path') ./base/centos-release/centos/srpm_path:mirror:Source/centos-release-7-4.1708.el7.centos.src.rpm ./base/lshell/centos/srpm_path:mirror:Source/lshell-0.9.16-5.el7.src.rpm ./base/setup/centos/srpm_path:mirror:Source/setup-2.8.71-7.el7.src.rpm ./base/libevent/centos/srpm_path:mirror:Source/libevent-2.0.21-4.el7.src.rpm ./base/dhcp/centos/srpm_path:mirror:Source/dhcp-4.2.5-58.el7.centos.src.rpm ./base/openssh/centos/srpm_path:mirror:Source/openssh-7.4p1-12.el7_4.src.rpm ./base/initscripts/centos/srpm_path:mirror:Source/initscripts-9.49.39-1.el7.src.rpm ./base/util-linux/centos/srpm_path:mirror:Source/util-linux-2.23.2-43.el7.src.rpm ./base/vim/centos/srpm_path:mirror:Source/vim-7.4.160-2.el7.src.rpm ./base/lighttpd/centos/srpm_path:mirror:Source/lighttpd-1.4.45-1.el7.src.rpm ./base/novnc/centos/srpm_path:mirror:Source/novnc-0.6.2-1.el7.src.rpm ./base/ntp/centos/srpm_path:mirror:Source/ntp-4.2.6p5-25.el7.centos.2.src.rpm ./base/pam/centos/srpm_path:mirror:Source/pam-1.1.8-18.el7.src.rpm ./base/sanlock/centos/srpm_path:mirror:Source/sanlock-3.5.0-1.el7.src.rpm ./base/shadow-utils/centos/srpm_path:mirror:Source/shadow-utils-4.1.5.1-24.el7.src.rpm ./base/sudo/centos/srpm_path:mirror:Source/sudo-1.8.19p2-11.el7_4.src.rpm ./base/systemd/centos/srpm_path:mirror:Source/systemd-219-42.el7_4.1.src.rpm ./base/watchdog/centos/srpm_path:mirror:Source/watchdog-5.13-11.el7.src.rpm ./base/net-snmp/centos/srpm_path:mirror:Source/net-snmp-5.7.2-28.el7.src.rpm ./base/memcached/centos/srpm_path:mirror:Source/memcached-1.4.39-1.el7.src.rpm ./base/cluster-resource-agents/centos/srpm_path:mirror:Source/resource-agents-3.9.5-105.el7.src.rpm ./base/bash/centos/srpm_path:mirror:Source/bash-4.2.46-29.el7_4.src.rpm ./base/haproxy/centos/srpm_path:mirror:Source/haproxy-1.5.18-6.el7.src.rpm ./base/netpbm/centos/srpm_path:mirror:Source/netpbm-10.61.02-9.el7.src.rpm ./base/anaconda/centos/srpm_path:mirror:Source/anaconda-21.48.22.121-1.el7.centos.src.rpm ./base/crontabs/centos/srpm_path:mirror:Source/crontabs-1.11-6.20121102git.el7.src.rpm ./base/dnsmasq/centos/srpm_path:mirror:Source/dnsmasq-2.76-2.el7_4.2.src.rpm ./base/rsync/centos/srpm_path:mirror:Source/rsync-3.0.9-18.el7.src.rpm ./kubernetes/docker-ce/centos/srpm_path:mirror:Source/docker-ce-18.03.1.ce-1.el7.centos.src.rpm ./kubernetes/kubernetes/centos/srpm_path:mirror:Source/kubernetes-1.10.0-1.el7.src.rpm ./networking/openvswitch/centos/srpm_path:mirror:/Source/openvswitch-2.9.0-3.el7.src.rpm ./networking/scapy/centos/srpm_path:mirror:Source/scapy-2.3.3-1.el7.src.rpm ./networking/iproute/centos/srpm_path:mirror:Source/iproute-3.10.0-87.el7.src.rpm ./networking/net-tools/centos/srpm_path:mirror:Source/net-tools-2.0-0.22.20131004git.el7.src.rpm ./networking/iptables/centos/srpm_path:mirror:Source/iptables-1.4.21-18.0.1.el7.centos.src.rpm ./python/python-eventlet/centos/srpm_path:mirror:Source/python-eventlet-0.18.4-2.el7.src.rpm ./python/python-requests/centos/srpm_path:mirror:Source/python-requests-2.14.2-1.el7.src.rpm ./python/python-django/centos/srpm_path:mirror:Source/python-django-1.8.14-1.el7.src.rpm ./python/python-gunicorn/centos/srpm_path:mirror:Source/python-gunicorn-19.7.1-1.fc27.src.rpm ./python/python-2.7.5/centos/srpm_path:mirror:Source/python-2.7.5-58.el7.src.rpm ./security/audit/centos/srpm_path:mirror:Source/audit-2.7.6-3.el7.src.rpm ./security/tpm2-tools/centos/srpm_path:mirror:Source/tpm2-tools-1.1.0-7.el7.src.rpm ./security/shim-signed/centos/srpm_path:mirror:Source/shim-signed-12-1.el7.centos.src.rpm ./security/shim-unsigned/centos/srpm_path:mirror:Source/shim-12-1.el7.centos.src.rpm ./security/tboot/centos/srpm_path:mirror:Source/tboot-1.9.5-1.el7.src.rpm ./security/python-keyring/centos/srpm_path:mirror:Source/python-keyring-5.7.1-1.el7.src.rpm ./kernel/kernel-std/centos/srpm_path:mirror:Source/kernel-3.10.0-862.3.2.el7.src.rpm ./kernel/kernel-rt/centos/srpm_path:mirror:Source/kernel-rt-3.10.0-862.3.2.rt56.808.el7.src.rpm ./logging/syslog-ng/centos/srpm_path:mirror:Source/syslog-ng-3.5.6-3.el7.src.rpm ./logging/logrotate/centos/srpm_path:mirror:Source/logrotate-3.8.6-14.el7.src.rpm ./ldap/nss-pam-ldapd/centos/srpm_path:mirror:Source/nss-pam-ldapd-0.8.13-8.el7.src.rpm ./ldap/openldap/centos/srpm_path:mirror:Source/openldap-2.4.44-5.el7.src.rpm ./filesystem/nfs-utils/centos/srpm_path:mirror:Source/nfs-utils-1.3.0-0.48.el7.src.rpm ./filesystem/e2fsprogs/centos/srpm_path:mirror:Source/e2fsprogs-1.42.9-10.el7.src.rpm ./filesystem/iscsi-initiator-utils/centos/srpm_path:mirror:Source/iscsi-initiator-utils-6.2.0.874-4.el7.src.rpm ./filesystem/parted/centos/srpm_path:mirror:Source/parted-3.1-28.el7.src.rpm ./config/puppet-4.8.2/centos/srpm_path:mirror:Source/puppet-4.8.2-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-ceilometer-11.3.0/centos/srpm_path:mirror:Source/puppet-ceilometer-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-ceph-2.2.0/centos/srpm_path:mirror:Source/puppet-ceph-2.2.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-cinder-11.3.0/centos/srpm_path:mirror:Source/puppet-cinder-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-glance-11.3.0/centos/srpm_path:mirror:Source/puppet-glance-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-heat-11.3.0/centos/srpm_path:mirror:Source/puppet-heat-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-horizon-9.5.0/centos/srpm_path:mirror:Source/puppet-horizon-9.5.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-ironic-11.3.0/centos/srpm_path:mirror:Source/puppet-ironic-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-keystone-11.3.0/centos/srpm_path:mirror:Source/puppet-keystone-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-magnum-11.3.0/centos/srpm_path:mirror:Source/puppet-magnum-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-memcached-3.0.2/centos/srpm_path:mirror:Source/puppet-memcached-3.0.2-1.adf8b63git.el7.src.rpm ./config/puppet-modules/openstack/puppet-murano-11.3.0/centos/srpm_path:mirror:Source/puppet-murano-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-neutron-11.3.0/centos/srpm_path:mirror:Source/puppet-neutron-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-nova-11.4.0/centos/srpm_path:mirror:Source/puppet-nova-11.4.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-openstacklib-11.3.0/centos/srpm_path:mirror:Source/puppet-openstacklib-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-oslo-11.3.0/centos/srpm_path:mirror:Source/puppet-oslo-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-panko-11.3.0/centos/srpm_path:mirror:Source/puppet-panko-11.3.0-1.el7.src.rpm ./config/puppet-modules/openstack/puppet-swift-11.3.0/centos/srpm_path:mirror:Source/puppet-swift-11.3.0-1.el7.src.rpm ./config/puppet-modules/puppet-haproxy-1.5.0/centos/srpm_path:mirror:Source/puppet-haproxy-1.5.0-2.6ee8180git.el7.src.rpm ./config/puppet-modules/puppet-rabbitmq-5.5.0/centos/srpm_path:mirror:Source/puppet-rabbitmq-5.6.0-4.5ac45degit.el7.src.rpm ./config/puppet-modules/puppet-staging/centos/srpm_path:mirror:Source/puppet-staging-1.0.4-1.b466d93git.el7.src.rpm ./config/puppet-modules/puppet-stdlib-4.12.0/centos/srpm_path:mirror:Source/puppet-stdlib-4.13.1-2.dcef77agit.el7.src.rpm ./config/facter/centos/srpm_path:mirror:Source/facter-2.4.4-4.el7.src.rpm ./virt/libvirt-python/centos/srpm_path:mirror:Source/libvirt-python-3.5.0-1.fc24.src.rpm ./virt/cloud-init/centos/srpm_path:mirror:Source/cloud-init-0.7.9-9.el7.centos.2.src.rpm ./grub/grubby/centos/srpm_path:mirror:Source/grubby-8.28-23.el7.src.rpm ./grub/grub2/centos/srpm_path:mirror:Source/grub2-2.02-0.64.el7.centos.src.rpm ./database/python-psycopg2/centos/srpm_path:mirror:Source/python-psycopg2-2.5.1-3.el7.src.rpm On 18-07-17 03:56 PM, Saul Wold wrote:
On 07/17/2018 12:25 PM, Scott Little wrote:
The full list of packages in stx-integ after proposed changes
Thanks, this help me understand some of the context and content in the re-arranged packages.
I understand your thought of functionality over upstream source, but it would make it clearer, especially for the OS upstream bits to all be contained in "base". That way we work so reduce that one directory to zero.
I am not going to block, just saying. I am currently pursuing the existing stx tree trying to understand some of the changes. I will send email on those later.
Sau!
On 18-07-17 03:10 PM, Scott Little wrote:
On 18-07-17 12:38 PM, Saul Wold wrote:
Do you have a full "after" list, that might help then just seeing what's being relocated.
[SL] will send seperately
base/anaconda base/bash base/centos-release base/cgcs-users base/cluster-resource-agents base/crontabs base/dhcp base/dnsmasq base/dpkg base/haproxy base/initscripts base/libevent base/libfdt base/lighttpd base/lshell base/memcached base/netpbm base/net-snmp base/novnc base/ntp base/openssh base/pam base/rpm base/rsync base/sanlock base/setup base/shadow-utils base/sudo base/systemd base/util-linux base/vim base/watchdog
ceph/python-cephclient
config/facter config/puppet-4.8.2 config/puppet-modules/openstack/puppet-ceilometer-11.3.0 config/puppet-modules/openstack/puppet-ceph-2.2.0 config/puppet-modules/openstack/puppet-cinder-11.3.0 config/puppet-modules/openstack/puppet-glance-11.3.0 config/puppet-modules/openstack/puppet-heat-11.3.0 config/puppet-modules/openstack/puppet-horizon-9.5.0 config/puppet-modules/openstack/puppet-ironic-11.3.0 config/puppet-modules/openstack/puppet-keystone-11.3.0 config/puppet-modules/openstack/puppet-magnum-11.3.0 config/puppet-modules/openstack/puppet-memcached-3.0.2 config/puppet-modules/openstack/puppet-murano-11.3.0 config/puppet-modules/openstack/puppet-neutron-11.3.0 config/puppet-modules/openstack/puppet-nova-11.4.0 config/puppet-modules/openstack/puppet-openstacklib-11.3.0 config/puppet-modules/openstack/puppet-oslo-11.3.0 config/puppet-modules/openstack/puppet-panko-11.3.0 config/puppet-modules/openstack/puppet-swift-11.3.0 config/puppet-modules/puppet-boolean-1.0.2 config/puppet-modules/puppet-create_resources config/puppet-modules/puppet-dnsmasq config/puppet-modules/puppet-drbd-0.3.1 config/puppet-modules/puppet-filemapper config/puppet-modules/puppet-haproxy-1.5.0 config/puppet-modules/puppet-ldap config/puppet-modules/puppet-lvm config/puppet-modules/puppet-network config/puppet-modules/puppet-nslcd config/puppet-modules/puppet-postgresql-4.8.0 config/puppet-modules/puppet-puppi config/puppet-modules/puppet-rabbitmq-5.5.0 config/puppet-modules/puppet-staging config/puppet-modules/puppet-stdlib-4.12.0
config-files/io-scheduler
database/mariadb database/python-psycopg2
filesystem/drbd/drbd-tools filesystem/e2fsprogs filesystem/filesystem-scripts filesystem/iscsi-initiator-utils filesystem/nfscheck filesystem/nfs-utils filesystem/parted
grub/grub2 grub/grubby
kernel/kernel-rt kernel/kernel-std
kernel/kernel-modules/drbd kernel/kernel-modules/integrity kernel/kernel-modules/intel-e1000e kernel/kernel-modules/intel-i40e kernel/kernel-modules/intel-i40evf kernel/kernel-modules/intel-ixgbe kernel/kernel-modules/intel-ixgbevf kernel/kernel-modules/mlnx-ofa_kernel kernel/kernel-modules/qat17 kernel/kernel-modules/tpmdd
kubernetes/docker-ce kubernetes/kubernetes
ldap/ldapscripts ldap/nss-pam-ldapd ldap/openldap
logging/logmgmt logging/logrotate logging/syslog-ng
monitoring/collectd-extensions monitoring/influxdb-extensions
networking/iproute networking/iptables networking/lldpd networking/mellanox/libibverbs networking/mellanox/libmlx4 networking/mellanox/libmlx5 networking/mellanox/mlx4-config networking/mellanox/rdma-core networking/net-tools networking/openvswitch networking/python-ryu networking/scapy
python/python-2.7.5 python/python-django python/python-eventlet python/python-gunicorn python/python-requests python/python-setuptools python/python-smartpm
restapi-doc
security/audit security/libtpms security/python-keyring security/shim-signed security/shim-unsigned security/spectre-meltdown-checker security/swtpm security/tboot security/tpm2-openssl-engine security/tpm2-tools security/tss2 security/wrs-ssl
strorage-drivers/python-3parclient strorage-drivers/python-lefthandclient
tools/collector tools/engtools/hostdata-collectors tools/monitor-tools tools/vm-topology
utilities/branding utilities/build-info utilities/namespace-utils utilities/nova-utils utilities/platform-util utilities/tis-extensions utilities/update-motd
virt/cloud-init virt/libvirt virt/libvirt-python virt/qemu
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On Tue, Jul 17, 2018 at 2:10 PM, Scott Little <scott.little@windriver.com> wrote:
On 18-07-17 12:38 PM, Saul Wold wrote:
A simple high level question, would it make sense to segregate out everything that is CentOS into base? That way as we move to more of an OS independent setup, the core directory could possibly go away?
[SL] We were envisioning function rather than upstream source as the reason for the categories. 'Base' are those packages that are pretty much universal to a Linux server.
I haven't compared RHEL directly to Ubuntu in a number of years in this regard but there used to be the kinds of differences that just made things frustrating. WRS has been through the Yocto -> CentOS mapping already, maybe that was smoother than I am imagining? I lean toward abstracting the distro layer as much as possible with a small list of exceptions (kernel, libvirt,, qemu, etc) that need special attention. this can always be done later though, I don't see anything here that makes it harder down the road, if we can make it easier that might be a win.
[SL] Tools vs utilities. Not clear I'll admit. Utilities are small, special purpose, shortcuts that could otherwise be accomplished by the right set of CLI commands. Tools are bigger, more complex, e.g. investigating and analyze the state of the system.
FWIW, I names stx-tools with the distinction of 'things used to _build_ the system' as opposed to 'things used to operate/diagnose the system'.
Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review?
We need to stick to the review process as much as possible, we're already getting into some bad habits that will be hard to break. I think it would be useful to post the reviews as soon as possible and mark them WIP (workflow -1) so they don't merge. That's where the specific discussions about tweaks can/should happen. Also, if the reviews for each repo are stacked we can build a manifest file to pull the reviews directly from Gerrit and actually test a build before merging it. dt -- Dean Troyer dtroyer@gmail.com
On 18-07-17 03:55 PM, Dean Troyer wrote:
We need to stick to the review process as much as possible, we're already getting into some bad habits that will be hard to break.
I think it would be useful to post the reviews as soon as possible and mark them WIP (workflow -1) so they don't merge. That's where the specific discussions about tweaks can/should happen.
Also, if the reviews for each repo are stacked we can build a manifest file to pull the reviews directly from Gerrit and actually test a build before merging it.
My challenge is trying to not disrupt the next set of updates being back ported to StarlingX from Titanium. If I go and re-arrange everything, their patch sets won't apply. Conversely their updates will break many of the relocation patches if they were created based on todays content. The model I've adopted is to create scripts to perform all the relocations. I can generate the relocation patches in a hurry. I'll run the script as soon as the last titanium back port is accepted or abandoned. The result will be a blizzard of reviews of content that's already been reviewed. The internal stx-integ relocations with 'git mv' are trivial enough. However, package moves between repos will look like large blocks of all new code, when it's nothing of the sort. The only competent reviewer is likely another script that runs diff a lot. My fears are: 1) Standard reviews will just invite lots of comments on the code content, rather than it's location and a few path changes. Those battles should already have been fought when the code was delivered to it's original location. 2) A long review process might prevent Titanium from converging, forcing a third back port cycle. Hoping someone has suggestions .... Scott
Revised timeline is August 1 or 2. Scott On 18-07-17 11:07 AM, Scott Little wrote:
Story: https://storyboard.openstack.org/#!/story/2002801
*Goals:*
1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils
2) Restructure the directories under which packages are to be found.
Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up.
Directories should descriptive of the class of packages to be found within.
Intent is to preserve update history as best is is possible.
*Timeline: *
Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed.
*Code Reviews: *
Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review?
*Details of directories/groups ...*
Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt
Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security
Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support
*Details of packages ...*
Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog
ceph/ python-cephclient
config/ e2fsprogs facter nfs-utils nfscheck puppet-4.8.2 puppet-modules
kernel/ kernel-std kernel-rt
kernel/kernel-modules/ mlnx-ofa_kernel
ldap/ nss-pam-ldapd openldap
logging/ syslog-ng logrotate
networking/ lldpd iproute mellanox python-ryu mlx4-config
python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm
security/ shim-signed shim-unsigned tboot
strorage-drivers/ python-3parclient python-lefthandclient
virt/ cloud-init libvirt libvirt-python qemu
tools/ storage-topology vm-topology
utilities/ tis-extensions namespace-utils nova-utils update-motd
Relocated packages (stx-utils to stx-update): enable-dev-patch
Relocated packages (stx-utils to stx-integ):
config-files/ io-scheduler
filesystem/ filesystem-scripts
grub/ grubby
logging/ logmgmt
tools/ collector monitor-tools
tools/engtools/ hostdata-collectors parsers
utilities/ build-info branding (formerly wrs-branding) platform-util
Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm
database/ mariadb
filesystem/ iscsi-initiator-utils
filesystem/drbd/ drbd-tools
kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd
ldap/ ldapscripts
networking/ iptables net-tools
Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync
database/ python-psycopg2
filesystem/ parted
grub/ grub2
security/ python-keyring
Delete two packages from stx-integ: tgt irqbalance
Delete two packages from stx-gplv3: seabios sysvinit
Delete one package from stx-utils: io-monitor
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
99% of the reviews are now available. I've held back the manifest changes for tomorrow. The relocation updates come in sets for each package, that attempt to preserve the update history found at the original location. One update removes a package from stx-utils, stx-gplv2, stx-gplv3. A second adds it to stx-integ or stx-updates in it's StarlingX day zero form (author changes from Dean to Me). Then there may be 0-N updates replaying the subsequent commit history of that package (author and commit text preserved). Finally there might be a follow up commit by me to fix a build path. The final result is a glorified 'mv' operation. The content should be unchanged, So all the code has been reviewed before. Reviews should focus one subject only, was the move executed correctly? Please do not workflow +1! I couldn't get the scripts to manage Depends-On relationships satisfactorily, so I'll hand manage it tomorrow. Scott On 18-07-31 11:26 AM, Scott Little wrote:
Revised timeline is August 1 or 2.
Scott
On 18-07-17 11:07 AM, Scott Little wrote:
Story: https://storyboard.openstack.org/#!/story/2002801
*Goals:*
1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils
2) Restructure the directories under which packages are to be found.
Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up.
Directories should descriptive of the class of packages to be found within.
Intent is to preserve update history as best is is possible.
*Timeline: *
Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed.
*Code Reviews: *
Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review?
*Details of directories/groups ...*
Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt
Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security
Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support
*Details of packages ...*
Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog
ceph/ python-cephclient
config/ e2fsprogs facter nfs-utils nfscheck puppet-4.8.2 puppet-modules
kernel/ kernel-std kernel-rt
kernel/kernel-modules/ mlnx-ofa_kernel
ldap/ nss-pam-ldapd openldap
logging/ syslog-ng logrotate
networking/ lldpd iproute mellanox python-ryu mlx4-config
python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm
security/ shim-signed shim-unsigned tboot
strorage-drivers/ python-3parclient python-lefthandclient
virt/ cloud-init libvirt libvirt-python qemu
tools/ storage-topology vm-topology
utilities/ tis-extensions namespace-utils nova-utils update-motd
Relocated packages (stx-utils to stx-update): enable-dev-patch
Relocated packages (stx-utils to stx-integ):
config-files/ io-scheduler
filesystem/ filesystem-scripts
grub/ grubby
logging/ logmgmt
tools/ collector monitor-tools
tools/engtools/ hostdata-collectors parsers
utilities/ build-info branding (formerly wrs-branding) platform-util
Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm
database/ mariadb
filesystem/ iscsi-initiator-utils
filesystem/drbd/ drbd-tools
kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd
ldap/ ldapscripts
networking/ iptables net-tools
Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync
database/ python-psycopg2
filesystem/ parted
grub/ grub2
security/ python-keyring
Delete two packages from stx-integ: tgt irqbalance
Delete two packages from stx-gplv3: seabios sysvinit
Delete one package from stx-utils: io-monitor
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Remaining reviews are now available: stx-manifests: https://review.openstack.org/588633 Remove empty repos stx-gplv2 and stx-gplv3 stx-manifests: https://review.openstack.org/588634 Remove empty repo stx-utils stx-root: https://review.openstack.org/588635 Remove empty repo stx-utils On 18-08-01 05:03 PM, Scott Little wrote:
99% of the reviews are now available. I've held back the manifest changes for tomorrow.
The relocation updates come in sets for each package, that attempt to preserve the update history found at the original location. One update removes a package from stx-utils, stx-gplv2, stx-gplv3. A second adds it to stx-integ or stx-updates in it's StarlingX day zero form (author changes from Dean to Me). Then there may be 0-N updates replaying the subsequent commit history of that package (author and commit text preserved). Finally there might be a follow up commit by me to fix a build path. The final result is a glorified 'mv' operation. The content should be unchanged, So all the code has been reviewed before.
Reviews should focus one subject only, was the move executed correctly?
Please do not workflow +1! I couldn't get the scripts to manage Depends-On relationships satisfactorily, so I'll hand manage it tomorrow.
Scott
On 18-07-31 11:26 AM, Scott Little wrote:
Revised timeline is August 1 or 2.
Scott
On 18-07-17 11:07 AM, Scott Little wrote:
Story: https://storyboard.openstack.org/#!/story/2002801
*Goals:*
1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils
2) Restructure the directories under which packages are to be found.
Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up.
Directories should descriptive of the class of packages to be found within.
Intent is to preserve update history as best is is possible.
*Timeline: *
Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed.
*Code Reviews: *
Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review?
*Details of directories/groups ...*
Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt
Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security
Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support
*Details of packages ...*
Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog
ceph/ python-cephclient
config/ e2fsprogs facter nfs-utils nfscheck puppet-4.8.2 puppet-modules
kernel/ kernel-std kernel-rt
kernel/kernel-modules/ mlnx-ofa_kernel
ldap/ nss-pam-ldapd openldap
logging/ syslog-ng logrotate
networking/ lldpd iproute mellanox python-ryu mlx4-config
python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm
security/ shim-signed shim-unsigned tboot
strorage-drivers/ python-3parclient python-lefthandclient
virt/ cloud-init libvirt libvirt-python qemu
tools/ storage-topology vm-topology
utilities/ tis-extensions namespace-utils nova-utils update-motd
Relocated packages (stx-utils to stx-update): enable-dev-patch
Relocated packages (stx-utils to stx-integ):
config-files/ io-scheduler
filesystem/ filesystem-scripts
grub/ grubby
logging/ logmgmt
tools/ collector monitor-tools
tools/engtools/ hostdata-collectors parsers
utilities/ build-info branding (formerly wrs-branding) platform-util
Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm
database/ mariadb
filesystem/ iscsi-initiator-utils
filesystem/drbd/ drbd-tools
kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd
ldap/ ldapscripts
networking/ iptables net-tools
Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync
database/ python-psycopg2
filesystem/ parted
grub/ grub2
security/ python-keyring
Delete two packages from stx-integ: tgt irqbalance
Delete two packages from stx-gplv3: seabios sysvinit
Delete one package from stx-utils: io-monitor
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On Fri, Aug 3, 2018 at 1:18 PM, Scott Little <scott.little@windriver.com> wrote:
Remaining reviews are now available:
stx-manifests: https://review.openstack.org/588633 Remove empty repos stx-gplv2 and stx-gplv3 stx-manifests: https://review.openstack.org/588634 Remove empty repo stx-utils stx-root: https://review.openstack.org/588635 Remove empty repo stx-utils
Looks good, thanks Scott! Is there a plan to change the cgcs-root directory name yet? dt -- Dean Troyer dtroyer@gmail.com
I'm looking at it for sure. That one will be really messy. Affecting not just git managed code, but wikis, in house jenkins jobs, and some prototype code to improve the rpm download issues that's likely more urgent. I'll call that round 3. On 18-08-03 02:33 PM, Dean Troyer wrote:
On Fri, Aug 3, 2018 at 1:18 PM, Scott Little <scott.little@windriver.com> wrote:
Remaining reviews are now available:
stx-manifests: https://review.openstack.org/588633 Remove empty repos stx-gplv2 and stx-gplv3 stx-manifests: https://review.openstack.org/588634 Remove empty repo stx-utils stx-root: https://review.openstack.org/588635 Remove empty repo stx-utils Looks good, thanks Scott!
Is there a plan to change the cgcs-root directory name yet?
dt
On Fri, Aug 3, 2018 at 1:36 PM, Scott Little <scott.little@windriver.com> wrote:
That one will be really messy. Affecting not just git managed code, but wikis, in house jenkins jobs, and some prototype code to improve the rpm download issues that's likely more urgent.
I'll call that round 3.
Sure, I didn't know if it was still in the queue. This looks great and is much easier to grok, thanks for the ton of effort that went in to it! dt -- Dean Troyer dtroyer@gmail.com
This is something that needs to be done but was not planned for this round. We can schedule later. Brent -----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: Friday, August 3, 2018 2:37 PM To: Dean Troyer <dtroyer@gmail.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Restructuring round 2 I'm looking at it for sure. That one will be really messy. Affecting not just git managed code, but wikis, in house jenkins jobs, and some prototype code to improve the rpm download issues that's likely more urgent. I'll call that round 3. On 18-08-03 02:33 PM, Dean Troyer wrote:
On Fri, Aug 3, 2018 at 1:18 PM, Scott Little <scott.little@windriver.com> wrote:
Remaining reviews are now available:
stx-manifests: https://review.openstack.org/588633 Remove empty repos stx-gplv2 and stx-gplv3 stx-manifests: https://review.openstack.org/588634 Remove empty repo stx-utils stx-root: https://review.openstack.org/588635 Remove empty repo stx-utils Looks good, thanks Scott!
Is there a plan to change the cgcs-root directory name yet?
dt
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
build-iso failure. Looks like we still have a unexpected dependency on seabios from qemu. Trying to figure out if we missed a qemu update, or need to restore seabios temporarily ... Scott On 18-08-03 02:18 PM, Scott Little wrote:
Remaining reviews are now available:
stx-manifests: https://review.openstack.org/588633 Remove empty repos stx-gplv2 and stx-gplv3 stx-manifests: https://review.openstack.org/588634 Remove empty repo stx-utils stx-root: https://review.openstack.org/588635 Remove empty repo stx-utils
On 18-08-01 05:03 PM, Scott Little wrote:
99% of the reviews are now available. I've held back the manifest changes for tomorrow.
The relocation updates come in sets for each package, that attempt to preserve the update history found at the original location. One update removes a package from stx-utils, stx-gplv2, stx-gplv3. A second adds it to stx-integ or stx-updates in it's StarlingX day zero form (author changes from Dean to Me). Then there may be 0-N updates replaying the subsequent commit history of that package (author and commit text preserved). Finally there might be a follow up commit by me to fix a build path. The final result is a glorified 'mv' operation. The content should be unchanged, So all the code has been reviewed before.
Reviews should focus one subject only, was the move executed correctly?
Please do not workflow +1! I couldn't get the scripts to manage Depends-On relationships satisfactorily, so I'll hand manage it tomorrow.
Scott
On 18-07-31 11:26 AM, Scott Little wrote:
Revised timeline is August 1 or 2.
Scott
On 18-07-17 11:07 AM, Scott Little wrote:
Story: https://storyboard.openstack.org/#!/story/2002801
*Goals:*
1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils
2) Restructure the directories under which packages are to be found.
Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up.
Directories should descriptive of the class of packages to be found within.
Intent is to preserve update history as best is is possible.
*Timeline: *
Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed.
*Code Reviews: *
Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review?
*Details of directories/groups ...*
Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt
Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security
Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support
*Details of packages ...*
Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog
ceph/ python-cephclient
config/ e2fsprogs facter nfs-utils nfscheck puppet-4.8.2 puppet-modules
kernel/ kernel-std kernel-rt
kernel/kernel-modules/ mlnx-ofa_kernel
ldap/ nss-pam-ldapd openldap
logging/ syslog-ng logrotate
networking/ lldpd iproute mellanox python-ryu mlx4-config
python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm
security/ shim-signed shim-unsigned tboot
strorage-drivers/ python-3parclient python-lefthandclient
virt/ cloud-init libvirt libvirt-python qemu
tools/ storage-topology vm-topology
utilities/ tis-extensions namespace-utils nova-utils update-motd
Relocated packages (stx-utils to stx-update): enable-dev-patch
Relocated packages (stx-utils to stx-integ):
config-files/ io-scheduler
filesystem/ filesystem-scripts
grub/ grubby
logging/ logmgmt
tools/ collector monitor-tools
tools/engtools/ hostdata-collectors parsers
utilities/ build-info branding (formerly wrs-branding) platform-util
Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm
database/ mariadb
filesystem/ iscsi-initiator-utils
filesystem/drbd/ drbd-tools
kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd
ldap/ ldapscripts
networking/ iptables net-tools
Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync
database/ python-psycopg2
filesystem/ parted
grub/ grub2
security/ python-keyring
Delete two packages from stx-integ: tgt irqbalance
Delete two packages from stx-gplv3: seabios sysvinit
Delete one package from stx-utils: io-monitor
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
My repoquery isn’t showing anything that requires seabios: [dpenney@yow-dpenney-lx-vm1 /localdisk/designer/dpenney/starlingx-3/cgcs-root]$ repoquery --repofrompath cgcs,$MY_REPO/cgcs-centos-repo/Binary --repofrompath tis,$MY_WORKSPACE/std/rpmbuild/RPMS --whatrequires seabios [dpenney@yow-dpenney-lx-vm1 /localdisk/designer/dpenney/starlingx-3/cgcs-root]$ repoquery --repofrompath cgcs,$MY_REPO/cgcs-centos-repo/Binary --repofrompath tis,$MY_WORKSPACE/std/rpmbuild/RPMS --whatrequires seabios [dpenney@yow-dpenney-lx-vm1 /localdisk/designer/dpenney/starlingx-3/cgcs-root]$ repoquery --repofrompath cgcs,$MY_REPO/cgcs-centos-repo/Binary --repofrompath tis,$MY_WORKSPACE/std/rpmbuild/RPMS --provides seabios seabios = 1.11.0-2.el7 seabios(x86-64) = 1.11.0-2.el7 From: Scott Little [mailto:scott.little@windriver.com] Sent: Friday, August 03, 2018 4:45 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Restructuring round 2 build-iso failure. Looks like we still have a unexpected dependency on seabios from qemu. Trying to figure out if we missed a qemu update, or need to restore seabios temporarily ... Scott On 18-08-03 02:18 PM, Scott Little wrote: Remaining reviews are now available: stx-manifests: https://review.openstack.org/588633 Remove empty repos stx-gplv2 and stx-gplv3 stx-manifests: https://review.openstack.org/588634 Remove empty repo stx-utils stx-root: https://review.openstack.org/588635 Remove empty repo stx-utils On 18-08-01 05:03 PM, Scott Little wrote: 99% of the reviews are now available. I've held back the manifest changes for tomorrow. The relocation updates come in sets for each package, that attempt to preserve the update history found at the original location. One update removes a package from stx-utils, stx-gplv2, stx-gplv3. A second adds it to stx-integ or stx-updates in it's StarlingX day zero form (author changes from Dean to Me). Then there may be 0-N updates replaying the subsequent commit history of that package (author and commit text preserved). Finally there might be a follow up commit by me to fix a build path. The final result is a glorified 'mv' operation. The content should be unchanged, So all the code has been reviewed before. Reviews should focus one subject only, was the move executed correctly? Please do not workflow +1! I couldn't get the scripts to manage Depends-On relationships satisfactorily, so I'll hand manage it tomorrow. Scott On 18-07-31 11:26 AM, Scott Little wrote: Revised timeline is August 1 or 2. Scott On 18-07-17 11:07 AM, Scott Little wrote: Story: https://storyboard.openstack.org/#!/story/2002801<https://storyboard.openstack.org/#%21/story/2002801> Goals: 1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils 2) Restructure the directories under which packages are to be found. Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up. Directories should descriptive of the class of packages to be found within. Intent is to preserve update history as best is is possible. Timeline: Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed. Code Reviews: Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review? Details of directories/groups ... Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support Details of packages ... Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog ceph/ python-cephclient config/ e2fsprogs facter nfs-utils nfscheck puppet-4.8.2 puppet-modules kernel/ kernel-std kernel-rt kernel/kernel-modules/ mlnx-ofa_kernel ldap/ nss-pam-ldapd openldap logging/ syslog-ng logrotate networking/ lldpd iproute mellanox python-ryu mlx4-config python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm security/ shim-signed shim-unsigned tboot strorage-drivers/ python-3parclient python-lefthandclient virt/ cloud-init libvirt libvirt-python qemu tools/ storage-topology vm-topology utilities/ tis-extensions namespace-utils nova-utils update-motd Relocated packages (stx-utils to stx-update): enable-dev-patch Relocated packages (stx-utils to stx-integ): config-files/ io-scheduler filesystem/ filesystem-scripts grub/ grubby logging/ logmgmt tools/ collector monitor-tools tools/engtools/ hostdata-collectors parsers utilities/ build-info branding (formerly wrs-branding) platform-util Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm database/ mariadb filesystem/ iscsi-initiator-utils filesystem/drbd/ drbd-tools kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd ldap/ ldapscripts networking/ iptables net-tools Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync database/ python-psycopg2 filesystem/ parted grub/ grub2 security/ python-keyring Delete two packages from stx-integ: tgt irqbalance Delete two packages from stx-gplv3: seabios sysvinit Delete one package from stx-utils: io-monitor _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
seabios-bin, however… qemu-kvm-ev-10:2.10.0-0.tis.0.x86_64 seabios-0:1.10.2-3.el7_4.1.tis.2.x86_64 swtpm-0:0.1.0-2.tis.0.x86_64 From: Penney, Don [mailto:Don.Penney@windriver.com] Sent: Friday, August 03, 2018 4:55 PM To: Little, Scott; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Restructuring round 2 My repoquery isn’t showing anything that requires seabios: [dpenney@yow-dpenney-lx-vm1 /localdisk/designer/dpenney/starlingx-3/cgcs-root]$ repoquery --repofrompath cgcs,$MY_REPO/cgcs-centos-repo/Binary --repofrompath tis,$MY_WORKSPACE/std/rpmbuild/RPMS --whatrequires seabios [dpenney@yow-dpenney-lx-vm1 /localdisk/designer/dpenney/starlingx-3/cgcs-root]$ repoquery --repofrompath cgcs,$MY_REPO/cgcs-centos-repo/Binary --repofrompath tis,$MY_WORKSPACE/std/rpmbuild/RPMS --whatrequires seabios [dpenney@yow-dpenney-lx-vm1 /localdisk/designer/dpenney/starlingx-3/cgcs-root]$ repoquery --repofrompath cgcs,$MY_REPO/cgcs-centos-repo/Binary --repofrompath tis,$MY_WORKSPACE/std/rpmbuild/RPMS --provides seabios seabios = 1.11.0-2.el7 seabios(x86-64) = 1.11.0-2.el7 From: Scott Little [mailto:scott.little@windriver.com] Sent: Friday, August 03, 2018 4:45 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Restructuring round 2 build-iso failure. Looks like we still have a unexpected dependency on seabios from qemu. Trying to figure out if we missed a qemu update, or need to restore seabios temporarily ... Scott On 18-08-03 02:18 PM, Scott Little wrote: Remaining reviews are now available: stx-manifests: https://review.openstack.org/588633 Remove empty repos stx-gplv2 and stx-gplv3 stx-manifests: https://review.openstack.org/588634 Remove empty repo stx-utils stx-root: https://review.openstack.org/588635 Remove empty repo stx-utils On 18-08-01 05:03 PM, Scott Little wrote: 99% of the reviews are now available. I've held back the manifest changes for tomorrow. The relocation updates come in sets for each package, that attempt to preserve the update history found at the original location. One update removes a package from stx-utils, stx-gplv2, stx-gplv3. A second adds it to stx-integ or stx-updates in it's StarlingX day zero form (author changes from Dean to Me). Then there may be 0-N updates replaying the subsequent commit history of that package (author and commit text preserved). Finally there might be a follow up commit by me to fix a build path. The final result is a glorified 'mv' operation. The content should be unchanged, So all the code has been reviewed before. Reviews should focus one subject only, was the move executed correctly? Please do not workflow +1! I couldn't get the scripts to manage Depends-On relationships satisfactorily, so I'll hand manage it tomorrow. Scott On 18-07-31 11:26 AM, Scott Little wrote: Revised timeline is August 1 or 2. Scott On 18-07-17 11:07 AM, Scott Little wrote: Story: https://storyboard.openstack.org/#!/story/2002801<https://storyboard.openstack.org/#%21/story/2002801> Goals: 1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils 2) Restructure the directories under which packages are to be found. Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up. Directories should descriptive of the class of packages to be found within. Intent is to preserve update history as best is is possible. Timeline: Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed. Code Reviews: Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review? Details of directories/groups ... Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support Details of packages ... Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog ceph/ python-cephclient config/ e2fsprogs facter nfs-utils nfscheck puppet-4.8.2 puppet-modules kernel/ kernel-std kernel-rt kernel/kernel-modules/ mlnx-ofa_kernel ldap/ nss-pam-ldapd openldap logging/ syslog-ng logrotate networking/ lldpd iproute mellanox python-ryu mlx4-config python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm security/ shim-signed shim-unsigned tboot strorage-drivers/ python-3parclient python-lefthandclient virt/ cloud-init libvirt libvirt-python qemu tools/ storage-topology vm-topology utilities/ tis-extensions namespace-utils nova-utils update-motd Relocated packages (stx-utils to stx-update): enable-dev-patch Relocated packages (stx-utils to stx-integ): config-files/ io-scheduler filesystem/ filesystem-scripts grub/ grubby logging/ logmgmt tools/ collector monitor-tools tools/engtools/ hostdata-collectors parsers utilities/ build-info branding (formerly wrs-branding) platform-util Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm database/ mariadb filesystem/ iscsi-initiator-utils filesystem/drbd/ drbd-tools kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd ldap/ ldapscripts networking/ iptables net-tools Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync database/ python-psycopg2 filesystem/ parted grub/ grub2 security/ python-keyring Delete two packages from stx-integ: tgt irqbalance Delete two packages from stx-gplv3: seabios sysvinit Delete one package from stx-utils: io-monitor _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io<mailto:Starlingx-discuss@lists.starlingx.io> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
I think adding seavgabios-bin-1.11.0-2.el7.noarch.rpm <http://mirror.centos.org/centos-7/7.5.1804/os/x86_64/Packages/seavgabios-bin-1.11.0-2.el7.noarch.rpm> and seabios-bin-1.11.0-2.el7.noarch.rpm <http://mirror.centos.org/centos-7/7.5.1804/os/x86_64/Packages/seabios-bin-1.11.0-2.el7.noarch.rpm> to the .lst files will resolve it. Scott On 18-08-03 05:04 PM, Penney, Don wrote:
seabios-bin, however…
qemu-kvm-ev-10:2.10.0-0.tis.0.x86_64
seabios-0:1.10.2-3.el7_4.1.tis.2.x86_64
swtpm-0:0.1.0-2.tis.0.x86_64
*From:*Penney, Don [mailto:Don.Penney@windriver.com] *Sent:* Friday, August 03, 2018 4:55 PM *To:* Little, Scott; starlingx-discuss@lists.starlingx.io *Subject:* Re: [Starlingx-discuss] Restructuring round 2
My repoquery isn’t showing anything that requires seabios:
[dpenney@yow-dpenney-lx-vm1 /localdisk/designer/dpenney/starlingx-3/cgcs-root]$ repoquery --repofrompath cgcs,$MY_REPO/cgcs-centos-repo/Binary --repofrompath tis,$MY_WORKSPACE/std/rpmbuild/RPMS --whatrequires seabios
[dpenney@yow-dpenney-lx-vm1 /localdisk/designer/dpenney/starlingx-3/cgcs-root]$ repoquery --repofrompath cgcs,$MY_REPO/cgcs-centos-repo/Binary --repofrompath tis,$MY_WORKSPACE/std/rpmbuild/RPMS --whatrequires seabios
[dpenney@yow-dpenney-lx-vm1 /localdisk/designer/dpenney/starlingx-3/cgcs-root]$ repoquery --repofrompath cgcs,$MY_REPO/cgcs-centos-repo/Binary --repofrompath tis,$MY_WORKSPACE/std/rpmbuild/RPMS --provides seabios
seabios = 1.11.0-2.el7
seabios(x86-64) = 1.11.0-2.el7
*From:*Scott Little [mailto:scott.little@windriver.com] *Sent:* Friday, August 03, 2018 4:45 PM *To:* starlingx-discuss@lists.starlingx.io *Subject:* Re: [Starlingx-discuss] Restructuring round 2
build-iso failure. Looks like we still have a unexpected dependency on seabios from qemu. Trying to figure out if we missed a qemu update, or need to restore seabios temporarily ...
Scott
On 18-08-03 02:18 PM, Scott Little wrote:
Remaining reviews are now available:
stx-manifests: https://review.openstack.org/588633 Remove empty repos stx-gplv2 and stx-gplv3 stx-manifests: https://review.openstack.org/588634 Remove empty repo stx-utils stx-root: https://review.openstack.org/588635 Remove empty repo stx-utils
On 18-08-01 05:03 PM, Scott Little wrote:
99% of the reviews are now available. I've held back the manifest changes for tomorrow.
The relocation updates come in sets for each package, that attempt to preserve the update history found at the original location. One update removes a package from stx-utils, stx-gplv2, stx-gplv3. A second adds it to stx-integ or stx-updates in it's StarlingX day zero form (author changes from Dean to Me). Then there may be 0-N updates replaying the subsequent commit history of that package (author and commit text preserved). Finally there might be a follow up commit by me to fix a build path. The final result is a glorified 'mv' operation. The content should be unchanged, So all the code has been reviewed before.
Reviews should focus one subject only, was the move executed correctly?
Please do not workflow +1! I couldn't get the scripts to manage Depends-On relationships satisfactorily, so I'll hand manage it tomorrow.
Scott
On 18-07-31 11:26 AM, Scott Little wrote:
Revised timeline is August 1 or 2.
Scott
On 18-07-17 11:07 AM, Scott Little wrote:
Story: https://storyboard.openstack.org/#!/story/2002801 <https://storyboard.openstack.org/#%21/story/2002801>
*Goals:*
1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils
2) Restructure the directories under which packages are to be found.
Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up.
Directories should descriptive of the class of packages to be found within.
Intent is to preserve update history as best is is possible.
*Timeline: *
Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed.
*Code Reviews: *
Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review?
*Details of directories/groups ...*
Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt
Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security
Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support
*Details of packages ...*
Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog
ceph/ python-cephclient
config/ e2fsprogs facter nfs-utils nfscheck puppet-4.8.2 puppet-modules
kernel/ kernel-std kernel-rt
kernel/kernel-modules/ mlnx-ofa_kernel
ldap/ nss-pam-ldapd openldap
logging/ syslog-ng logrotate
networking/ lldpd iproute mellanox python-ryu mlx4-config
python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm
security/ shim-signed shim-unsigned tboot
strorage-drivers/ python-3parclient python-lefthandclient
virt/ cloud-init libvirt libvirt-python qemu
tools/ storage-topology vm-topology
utilities/ tis-extensions namespace-utils nova-utils update-motd
Relocated packages (stx-utils to stx-update): enable-dev-patch
Relocated packages (stx-utils to stx-integ):
config-files/ io-scheduler
filesystem/ filesystem-scripts
grub/ grubby
logging/ logmgmt
tools/ collector monitor-tools
tools/engtools/ hostdata-collectors parsers
utilities/ build-info branding (formerly wrs-branding) platform-util
Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm
database/ mariadb
filesystem/ iscsi-initiator-utils
filesystem/drbd/ drbd-tools
kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd
ldap/ ldapscripts
networking/ iptables net-tools
Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync
database/ python-psycopg2
filesystem/ parted
grub/ grub2
security/ python-keyring
Delete two packages from stx-integ: tgt irqbalance
Delete two packages from stx-gplv3: seabios sysvinit
Delete one package from stx-utils: io-monitor
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io <mailto:Starlingx-discuss@lists.starlingx.io>
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io <mailto:Starlingx-discuss@lists.starlingx.io>
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io <mailto:Starlingx-discuss@lists.starlingx.io>
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io <mailto:Starlingx-discuss@lists.starlingx.io>
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Yep, that's got it. Review is up. Scott On 18-08-03 05:06 PM, Scott Little wrote:
I think adding seavgabios-bin-1.11.0-2.el7.noarch.rpm <http://mirror.centos.org/centos-7/7.5.1804/os/x86_64/Packages/seavgabios-bin-1.11.0-2.el7.noarch.rpm> and seabios-bin-1.11.0-2.el7.noarch.rpm <http://mirror.centos.org/centos-7/7.5.1804/os/x86_64/Packages/seabios-bin-1.11.0-2.el7.noarch.rpm> to the .lst files will resolve it.
Scott
On 18-08-03 05:04 PM, Penney, Don wrote:
seabios-bin, however…
qemu-kvm-ev-10:2.10.0-0.tis.0.x86_64
seabios-0:1.10.2-3.el7_4.1.tis.2.x86_64
swtpm-0:0.1.0-2.tis.0.x86_64
*From:*Penney, Don [mailto:Don.Penney@windriver.com] *Sent:* Friday, August 03, 2018 4:55 PM *To:* Little, Scott; starlingx-discuss@lists.starlingx.io *Subject:* Re: [Starlingx-discuss] Restructuring round 2
My repoquery isn’t showing anything that requires seabios:
[dpenney@yow-dpenney-lx-vm1 /localdisk/designer/dpenney/starlingx-3/cgcs-root]$ repoquery --repofrompath cgcs,$MY_REPO/cgcs-centos-repo/Binary --repofrompath tis,$MY_WORKSPACE/std/rpmbuild/RPMS --whatrequires seabios
[dpenney@yow-dpenney-lx-vm1 /localdisk/designer/dpenney/starlingx-3/cgcs-root]$ repoquery --repofrompath cgcs,$MY_REPO/cgcs-centos-repo/Binary --repofrompath tis,$MY_WORKSPACE/std/rpmbuild/RPMS --whatrequires seabios
[dpenney@yow-dpenney-lx-vm1 /localdisk/designer/dpenney/starlingx-3/cgcs-root]$ repoquery --repofrompath cgcs,$MY_REPO/cgcs-centos-repo/Binary --repofrompath tis,$MY_WORKSPACE/std/rpmbuild/RPMS --provides seabios
seabios = 1.11.0-2.el7
seabios(x86-64) = 1.11.0-2.el7
*From:*Scott Little [mailto:scott.little@windriver.com] *Sent:* Friday, August 03, 2018 4:45 PM *To:* starlingx-discuss@lists.starlingx.io *Subject:* Re: [Starlingx-discuss] Restructuring round 2
build-iso failure. Looks like we still have a unexpected dependency on seabios from qemu. Trying to figure out if we missed a qemu update, or need to restore seabios temporarily ...
Scott
On 18-08-03 02:18 PM, Scott Little wrote:
Remaining reviews are now available:
stx-manifests: https://review.openstack.org/588633 Remove empty repos stx-gplv2 and stx-gplv3 stx-manifests: https://review.openstack.org/588634 Remove empty repo stx-utils stx-root: https://review.openstack.org/588635 Remove empty repo stx-utils
On 18-08-01 05:03 PM, Scott Little wrote:
99% of the reviews are now available. I've held back the manifest changes for tomorrow.
The relocation updates come in sets for each package, that attempt to preserve the update history found at the original location. One update removes a package from stx-utils, stx-gplv2, stx-gplv3. A second adds it to stx-integ or stx-updates in it's StarlingX day zero form (author changes from Dean to Me). Then there may be 0-N updates replaying the subsequent commit history of that package (author and commit text preserved). Finally there might be a follow up commit by me to fix a build path. The final result is a glorified 'mv' operation. The content should be unchanged, So all the code has been reviewed before.
Reviews should focus one subject only, was the move executed correctly?
Please do not workflow +1! I couldn't get the scripts to manage Depends-On relationships satisfactorily, so I'll hand manage it tomorrow.
Scott
On 18-07-31 11:26 AM, Scott Little wrote:
Revised timeline is August 1 or 2.
Scott
On 18-07-17 11:07 AM, Scott Little wrote:
Story: https://storyboard.openstack.org/#!/story/2002801 <https://storyboard.openstack.org/#%21/story/2002801>
*Goals:*
1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils
2) Restructure the directories under which packages are to be found.
Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up.
Directories should descriptive of the class of packages to be found within.
Intent is to preserve update history as best is is possible.
*Timeline: *
Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed.
*Code Reviews: *
Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review?
*Details of directories/groups ...*
Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt
Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security
Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support
*Details of packages ...*
Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog
ceph/ python-cephclient
config/ e2fsprogs facter nfs-utils nfscheck puppet-4.8.2 puppet-modules
kernel/ kernel-std kernel-rt
kernel/kernel-modules/ mlnx-ofa_kernel
ldap/ nss-pam-ldapd openldap
logging/ syslog-ng logrotate
networking/ lldpd iproute mellanox python-ryu mlx4-config
python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm
security/ shim-signed shim-unsigned tboot
strorage-drivers/ python-3parclient python-lefthandclient
virt/ cloud-init libvirt libvirt-python qemu
tools/ storage-topology vm-topology
utilities/ tis-extensions namespace-utils nova-utils update-motd
Relocated packages (stx-utils to stx-update): enable-dev-patch
Relocated packages (stx-utils to stx-integ):
config-files/ io-scheduler
filesystem/ filesystem-scripts
grub/ grubby
logging/ logmgmt
tools/ collector monitor-tools
tools/engtools/ hostdata-collectors parsers
utilities/ build-info branding (formerly wrs-branding) platform-util
Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm
database/ mariadb
filesystem/ iscsi-initiator-utils
filesystem/drbd/ drbd-tools
kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd
ldap/ ldapscripts
networking/ iptables net-tools
Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync
database/ python-psycopg2
filesystem/ parted
grub/ grub2
security/ python-keyring
Delete two packages from stx-integ: tgt irqbalance
Delete two packages from stx-gplv3: seabios sysvinit
Delete one package from stx-utils: io-monitor
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io <mailto:Starlingx-discuss@lists.starlingx.io>
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io <mailto:Starlingx-discuss@lists.starlingx.io>
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io <mailto:Starlingx-discuss@lists.starlingx.io>
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io <mailto:Starlingx-discuss@lists.starlingx.io>
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Two late additions to the restructuring list ... Move ceph and ceph-manager from stx-upstream to stx-integ/ceph/ Reviews have been posted. These are history preserving moves. ceph: https://review.openstack.org/591435 https://review.openstack.org/591428 https://review.openstack.org/591429 ceph-manager: https://review.openstack.org/591436 https://review.openstack.org/591430 https://review.openstack.org/591431 https://review.openstack.org/591432 https://review.openstack.org/591433 https://review.openstack.org/591434 Scott On 18-08-01 05:03 PM, Scott Little wrote:
99% of the reviews are now available. I've held back the manifest changes for tomorrow.
The relocation updates come in sets for each package, that attempt to preserve the update history found at the original location. One update removes a package from stx-utils, stx-gplv2, stx-gplv3. A second adds it to stx-integ or stx-updates in it's StarlingX day zero form (author changes from Dean to Me). Then there may be 0-N updates replaying the subsequent commit history of that package (author and commit text preserved). Finally there might be a follow up commit by me to fix a build path. The final result is a glorified 'mv' operation. The content should be unchanged, So all the code has been reviewed before.
Reviews should focus one subject only, was the move executed correctly?
Please do not workflow +1! I couldn't get the scripts to manage Depends-On relationships satisfactorily, so I'll hand manage it tomorrow.
Scott
On 18-07-31 11:26 AM, Scott Little wrote:
Revised timeline is August 1 or 2.
Scott
On 18-07-17 11:07 AM, Scott Little wrote:
Story: https://storyboard.openstack.org/#!/story/2002801
*Goals:*
1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils
2) Restructure the directories under which packages are to be found.
Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up.
Directories should descriptive of the class of packages to be found within.
Intent is to preserve update history as best is is possible.
*Timeline: *
Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed.
*Code Reviews: *
Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review?
*Details of directories/groups ...*
Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt
Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security
Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support
*Details of packages ...*
Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog
ceph/ python-cephclient
config/ e2fsprogs facter nfs-utils nfscheck puppet-4.8.2 puppet-modules
kernel/ kernel-std kernel-rt
kernel/kernel-modules/ mlnx-ofa_kernel
ldap/ nss-pam-ldapd openldap
logging/ syslog-ng logrotate
networking/ lldpd iproute mellanox python-ryu mlx4-config
python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm
security/ shim-signed shim-unsigned tboot
strorage-drivers/ python-3parclient python-lefthandclient
virt/ cloud-init libvirt libvirt-python qemu
tools/ storage-topology vm-topology
utilities/ tis-extensions namespace-utils nova-utils update-motd
Relocated packages (stx-utils to stx-update): enable-dev-patch
Relocated packages (stx-utils to stx-integ):
config-files/ io-scheduler
filesystem/ filesystem-scripts
grub/ grubby
logging/ logmgmt
tools/ collector monitor-tools
tools/engtools/ hostdata-collectors parsers
utilities/ build-info branding (formerly wrs-branding) platform-util
Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm
database/ mariadb
filesystem/ iscsi-initiator-utils
filesystem/drbd/ drbd-tools
kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd
ldap/ ldapscripts
networking/ iptables net-tools
Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync
database/ python-psycopg2
filesystem/ parted
grub/ grub2
security/ python-keyring
Delete two packages from stx-integ: tgt irqbalance
Delete two packages from stx-gplv3: seabios sysvinit
Delete one package from stx-utils: io-monitor
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
PS: Please leave the workflow +1 to me. On 18-08-13 11:49 AM, Scott Little wrote:
Two late additions to the restructuring list ...
Move ceph and ceph-manager from stx-upstream to stx-integ/ceph/
Reviews have been posted. These are history preserving moves.
ceph: https://review.openstack.org/591435 https://review.openstack.org/591428 https://review.openstack.org/591429
ceph-manager: https://review.openstack.org/591436 https://review.openstack.org/591430 https://review.openstack.org/591431 https://review.openstack.org/591432 https://review.openstack.org/591433 https://review.openstack.org/591434
Scott
On 18-08-01 05:03 PM, Scott Little wrote:
99% of the reviews are now available. I've held back the manifest changes for tomorrow.
The relocation updates come in sets for each package, that attempt to preserve the update history found at the original location. One update removes a package from stx-utils, stx-gplv2, stx-gplv3. A second adds it to stx-integ or stx-updates in it's StarlingX day zero form (author changes from Dean to Me). Then there may be 0-N updates replaying the subsequent commit history of that package (author and commit text preserved). Finally there might be a follow up commit by me to fix a build path. The final result is a glorified 'mv' operation. The content should be unchanged, So all the code has been reviewed before.
Reviews should focus one subject only, was the move executed correctly?
Please do not workflow +1! I couldn't get the scripts to manage Depends-On relationships satisfactorily, so I'll hand manage it tomorrow.
Scott
On 18-07-31 11:26 AM, Scott Little wrote:
Revised timeline is August 1 or 2.
Scott
On 18-07-17 11:07 AM, Scott Little wrote:
Story: https://storyboard.openstack.org/#!/story/2002801
*Goals:*
1) Consolidate the following repo’s under stx-integ. • stx-gplv2 • stx-gplv3 • stx-utils
2) Restructure the directories under which packages are to be found.
Currently stx-gplv2/3 are largely without structure. Parts of the stx-integ structure were inherited from WRLinux and make little sense. stx-utils is just i mess of stuff that never found a home when StarlingX was first set up.
Directories should descriptive of the class of packages to be found within.
Intent is to preserve update history as best is is possible.
*Timeline: *
Probably around July 23 unless there are strong objections. We should probably have a freeze on submissions to the affected repos until it is all completed.
*Code Reviews: *
Most of this is just moving code around. A few path corrections, but no new code. The number and size of the reviews will be huge, and the code should all have been inspected once before. Is there a way to fast track this? Would there be strong objections to me just doing a +2/+1 without waiting for independent review?
*Details of directories/groups ...*
Create new directories under stx-integ (logical groupings for files): ceph config config-files database filesystem filesystem/drbd grub kernel kernel/kernel-modules ldap logging strorage-drivers tools utilities virt
Retained directories under stx-integ (additional logical groupings for files): base mellanox monitoring networking python restapi-doc security
Retire directories under stx-integ (non-descriptive or ambiguous grouping we will retire): connectivity core devtools extended support
*Details of packages ...*
Relocated packages (internal to stx-integ): base/ dhcp initscripts libevent lighttpd memcached net-snmp novnc ntp openssh pam procps sanlock shadow sudo systemd util-linux vim watchdog
ceph/ python-cephclient
config/ e2fsprogs facter nfs-utils nfscheck puppet-4.8.2 puppet-modules
kernel/ kernel-std kernel-rt
kernel/kernel-modules/ mlnx-ofa_kernel
ldap/ nss-pam-ldapd openldap
logging/ syslog-ng logrotate
networking/ lldpd iproute mellanox python-ryu mlx4-config
python/ python-2.7.5 python-django python-gunicorn python-setuptools python-smartpm
security/ shim-signed shim-unsigned tboot
strorage-drivers/ python-3parclient python-lefthandclient
virt/ cloud-init libvirt libvirt-python qemu
tools/ storage-topology vm-topology
utilities/ tis-extensions namespace-utils nova-utils update-motd
Relocated packages (stx-utils to stx-update): enable-dev-patch
Relocated packages (stx-utils to stx-integ):
config-files/ io-scheduler
filesystem/ filesystem-scripts
grub/ grubby
logging/ logmgmt
tools/ collector monitor-tools
tools/engtools/ hostdata-collectors parsers
utilities/ build-info branding (formerly wrs-branding) platform-util
Relocated packages (stx-gpl2 to stx-integ): base/ bash cgcs-users cluster-resource-agents dpkg haproxy libfdt netpbm rpm
database/ mariadb
filesystem/ iscsi-initiator-utils
filesystem/drbd/ drbd-tools
kernel/kernel-modules/ drbd integrity intel-e1000e intel-i40e intel-i40evf intel-ixgbe intel-ixgbevf qat17 tpmdd
ldap/ ldapscripts
networking/ iptables net-tools
Relocated packages (stx-gpl3 to stx-integ): base/ anaconda crontabs dnsmasq rsync
database/ python-psycopg2
filesystem/ parted
grub/ grub2
security/ python-keyring
Delete two packages from stx-integ: tgt irqbalance
Delete two packages from stx-gplv3: seabios sysvinit
Delete one package from stx-utils: io-monitor
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (7)
-
Cordoba Malibran, Erich
-
Dean Troyer
-
Jones, Bruce E
-
Penney, Don
-
Rowsell, Brent
-
Saul Wold
-
Scott Little