[Starlingx-discuss] [build] StarlingX ISO file now available at our Cengn mirror
Hello community We have an ISO file available at our Cengn mirror so people who wants to start playing with the StarlingX project can do so. I want to give out special thanks to Scott Little and Jason McKenna for making this happen in such timely manner. The image is hosted at http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/ou... For more information about the mirror and other build and news from the build team please check our wiki. https://wiki.openstack.org/wiki/StarlingX/Build Regards Cesar Lara Software Engineering Manager OpenSource Technology Center
Hi Cesar, Thank you for sharing this great progress. With this, it’s more convenient for us to share ISO with customers who want to have a quick try. In addition, I would like to know whether or not Cengn has plan to share the *build mirrors* (RPMs, SRPMs, and other downloading packages) with community. If so, how soon will it be ready? Regards, Yong From: "Lara, Cesar" <cesar.lara@intel.com> Date: Wednesday, 14 November 2018 at 5:15 AM To: "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] [build] StarlingX ISO file now available at our Cengn mirror Hello community We have an ISO file available at our Cengn mirror so people who wants to start playing with the StarlingX project can do so. I want to give out special thanks to Scott Little and Jason McKenna for making this happen in such timely manner. The image is hosted at http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/ou... For more information about the mirror and other build and news from the build team please check our wiki. https://wiki.openstack.org/wiki/StarlingX/Build Regards Cesar Lara Software Engineering Manager OpenSource Technology Center
Yes, that will be coming soon. Scott On 18-11-13 07:44 PM, Hu, Yong wrote:
Hi Cesar,
Thank you for sharing this great progress. With this, it’s more convenient for us to share ISO with customers who want to have a quick try.
In addition, I would like to know whether or not Cengn has plan to share the **build mirrors** (RPMs, SRPMs, and other downloading packages) with community.
If so, how soon will it be ready?
Regards,
Yong
*From: *"Lara, Cesar" <cesar.lara@intel.com> *Date: *Wednesday, 14 November 2018 at 5:15 AM *To: *"starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> *Subject: *[Starlingx-discuss] [build] StarlingX ISO file now available at our Cengn mirror
Hello community
We have an ISO file available at our Cengn mirror so people who wants to start playing with the StarlingX project can do so. I want to give out special thanks to Scott Little and Jason McKenna for making this happen in such timely manner.
The image is hosted at
http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/ou...
For more information about the mirror and other build and news from the build team please check our wiki.
https://wiki.openstack.org/wiki/StarlingX/Build
Regards
*//*
*/Cesar Lara/*
Software Engineering Manager
OpenSource Technology Center
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
The spec should be posted soon. Until then... Proposed directory structure: http://mirror.starlingx.cengn.ca/mirror/starlingx/<path> <path> = <distro>/<release>/<build-date>/outputs/<output-artifact-type> <distro>/<release>/<build-date>/inputs/<input-artifact-type> <distro> = 'centos' 'ubuntu' 'clear_linux' <release> = 'master' <release-branch> <release-branch> = 2018.10 # dropping the 'r/' prefix ... <build-date> = $(date +%Y%m%dT%H%M%SZ) # time stamp of start of 'repo sync' <latest_build> # a symlink to the last successful build date <input-artifact-type> = RPMS/ SRPMS/ downloads/ <output-artifact-type> = RPMS/<build-phase>/ SRPMS/<build-phase>/ iso/ installer/ CONTEXT <container-artifacts> <build-result> logs/ <build-phase> = std rt installer container ... <container-artifacts> = TBD <build-result> = 'success' | 'fail' RPMS and SRPMS subdirectories will include repodata. Scott On 18-11-14 09:57 AM, Scott Little wrote:
Yes, that will be coming soon.
Scott
On 18-11-13 07:44 PM, Hu, Yong wrote:
Hi Cesar,
Thank you for sharing this great progress. With this, it’s more convenient for us to share ISO with customers who want to have a quick try.
In addition, I would like to know whether or not Cengn has plan to share the **build mirrors** (RPMs, SRPMs, and other downloading packages) with community.
If so, how soon will it be ready?
Regards,
Yong
*From: *"Lara, Cesar" <cesar.lara@intel.com> *Date: *Wednesday, 14 November 2018 at 5:15 AM *To: *"starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> *Subject: *[Starlingx-discuss] [build] StarlingX ISO file now available at our Cengn mirror
Hello community
We have an ISO file available at our Cengn mirror so people who wants to start playing with the StarlingX project can do so. I want to give out special thanks to Scott Little and Jason McKenna for making this happen in such timely manner.
The image is hosted at
http://mirror.starlingx.cengn.ca/mirror/starlingx/centos/2018.10/20181110/ou...
For more information about the mirror and other build and news from the build team please check our wiki.
https://wiki.openstack.org/wiki/StarlingX/Build
Regards
*//*
*/Cesar Lara/*
Software Engineering Manager
OpenSource Technology Center
_______________________________________________ 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, Nov 16, 2018 at 9:47 AM Scott Little <scott.little@windriver.com> wrote:
The spec should be posted soon. Until then... Proposed directory structure:> http://mirror.starlingx.cengn.ca/mirror/starlingx/<path>
<path> = <distro>/<release>/<build-date>/outputs/<output-artifact-type> <distro>/<release>/<build-date>/inputs/<input-artifact-type>
My instinct is to do <release>/<distro> because I tend to think in sorting by time more than type...but /me shrugs...
<distro> = 'centos' 'ubuntu' 'clear_linux'
The value for Clear Linux should match however the clear community self-identifies... Victor? /me does research In DevStack we are using 'clearlinux' while Clear's os-release file uses 'clear-linux-os'. I don't recall why those are different.
<release> = 'master' <release-branch>
<release-branch> = 2018.10 # dropping the 'r/' prefix
This maybe should be <release-tag> instead, the tags do not have prefixes, but do have a 'z' component: the actual release is 2018.10.0 and 2018.10.1 would be the next bug-fix release of r/2018.10 if we were to do one, that might be a useful distinction in the future. dt -- Dean Troyer dtroyer@gmail.com
Thanks for the input. The spec has been posted.... https://review.openstack.org/#/c/618587/1/specs/2019.03/approved/mirror_2003... Scott On 18-11-16 12:06 PM, Dean Troyer wrote:
On Fri, Nov 16, 2018 at 9:47 AM Scott Little <scott.little@windriver.com> wrote:
The spec should be posted soon. Until then... Proposed directory structure:> http://mirror.starlingx.cengn.ca/mirror/starlingx/<path>
<path> = <distro>/<release>/<build-date>/outputs/<output-artifact-type> <distro>/<release>/<build-date>/inputs/<input-artifact-type> My instinct is to do <release>/<distro> because I tend to think in sorting by time more than type...but /me shrugs...
<distro> = 'centos' 'ubuntu' 'clear_linux' The value for Clear Linux should match however the clear community self-identifies... Victor?
/me does research
In DevStack we are using 'clearlinux' while Clear's os-release file uses 'clear-linux-os'. I don't recall why those are different.
<release> = 'master' <release-branch>
<release-branch> = 2018.10 # dropping the 'r/' prefix This maybe should be <release-tag> instead, the tags do not have prefixes, but do have a 'z' component: the actual release is 2018.10.0 and 2018.10.1 would be the next bug-fix release of r/2018.10 if we were to do one, that might be a useful distinction in the future.
dt
On Fri, Nov 16, 2018 at 11:06 AM Dean Troyer <dtroyer@gmail.com> wrote:
On Fri, Nov 16, 2018 at 9:47 AM Scott Little <scott.little@windriver.com> wrote:
The spec should be posted soon. Until then... Proposed directory structure:> http://mirror.starlingx.cengn.ca/mirror/starlingx/<path>
<path> = <distro>/<release>/<build-date>/outputs/<output-artifact-type> <distro>/<release>/<build-date>/inputs/<input-artifact-type>
My instinct is to do <release>/<distro> because I tend to think in sorting by time more than type...but /me shrugs...
+1 on this , is better in my opinion <release>/<distro> for sorting and debuging in the future
<distro> = 'centos' 'ubuntu' 'clear_linux'
The value for Clear Linux should match however the clear community self-identifies... Victor?
as clear linux developer and user I love the idea of having clear linxu losted here , we are working on the enblment of STX with clearlinux
/me does research
In DevStack we are using 'clearlinux' while Clear's os-release file uses 'clear-linux-os'. I don't recall why those are different.
We use the os-release file from systemd , for example : $ cat /lib/os-release NAME="Clear Linux OS" VERSION=1 ID=clear-linux-os ID_LIKE=clear-linux-os VERSION_ID=26260 PRETTY_NAME="Clear Linux OS" ANSI_COLOR="1;35" HOME_URL="https://clearlinux.org" SUPPORT_URL="https://clearlinux.org" BUG_REPORT_URL="mailto:dev@lists.clearlinux.org" PRIVACY_POLICY_URL="http://www.intel.com/privacy" Whatever standard you prefer is fine
<release> = 'master' <release-branch>
<release-branch> = 2018.10 # dropping the 'r/' prefix
This maybe should be <release-tag> instead, the tags do not have prefixes, but do have a 'z' component: the actual release is 2018.10.0 and 2018.10.1 would be the next bug-fix release of r/2018.10 if we were to do one, that might be a useful distinction in the future.
dt
Regards
--
Dean Troyer dtroyer@gmail.com
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (5)
-
Dean Troyer
-
Hu, Yong
-
Lara, Cesar
-
Scott Little
-
Victor Rodriguez