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