[Starlingx-discuss] wrsroot -> sysadmin rebased reviews
Folks, I pushed the rebased reviews for the username change to this set of 5 repos: https://review.opendev.org/#/q/topic:wrsroot I have created an ISO that the Intel team is testing with, if other members can build an iso with an updated manifest to include these changes and test. Thanks Sau!
Hi I used the ISO provided by Saul and below are some findings on virtual environment. 1. Interfaces are named eth0 and eth1 instead of eth1000 and eth1001, this is breaking our automation flow 2. it never updates the `install_state` it always stays in `None` as our automation uses that value to monitor the installation progress it also fails 3. Hacking those 2 issues I was able to complete deployment and execute Sanity (using config_controller --force) without significant problems (I saw some issues but are related to my host machine resources rather than the functionality) Note: Issues 1 and 2 were not observed on any other ISOs recently validated. Regards, José
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Wednesday, May 29, 2019 1:03 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews
Folks,
I pushed the rebased reviews for the username change to this set of 5 repos:
https://review.opendev.org/#/q/topic:wrsroot
I have created an ISO that the Intel team is testing with, if other members can build an iso with an updated manifest to include these changes and test.
Thanks Sau!
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On 5/29/19 1:53 PM, Perez Carranza, Jose wrote:
Hi
I used the ISO provided by Saul and below are some findings on virtual environment.
1. Interfaces are named eth0 and eth1 instead of eth1000 and eth1001, this is breaking our automation flow I think this might be because I have an older installer, thoughts?
I am rebuilding the iso with updated installer files (squashfs.img, initrd.img and vmlinuz).
2. it never updates the `install_state` it always stays in `None` as our automation uses that value to monitor the installation progress it also fails Not sure how this one can be connected to wrsroot / sysadmin, if someone can point me a to a little further details of where this state change happens, I can take a look further into it. Maybe a permissions issue?
Sau!
3. Hacking those 2 issues I was able to complete deployment and execute Sanity (using config_controller --force) without significant problems (I saw some issues but are related to my host machine resources rather than the functionality)
Note: Issues 1 and 2 were not observed on any other ISOs recently validated.
Regards, José
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Wednesday, May 29, 2019 1:03 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews
Folks,
I pushed the rebased reviews for the username change to this set of 5 repos:
https://review.opendev.org/#/q/topic:wrsroot
I have created an ISO that the Intel team is testing with, if other members can build an iso with an updated manifest to include these changes and test.
Thanks Sau!
_______________________________________________ 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 install_state progress notifications are part of the StarlingX installer customizations to Anaconda. If you have the stock CentOS installer, you won't get these notifications. Likewise, this would likely explain issue #1. -----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Wednesday, May 29, 2019 7:11 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews On 5/29/19 1:53 PM, Perez Carranza, Jose wrote:
Hi
I used the ISO provided by Saul and below are some findings on virtual environment.
1. Interfaces are named eth0 and eth1 instead of eth1000 and eth1001, this is breaking our automation flow I think this might be because I have an older installer, thoughts?
I am rebuilding the iso with updated installer files (squashfs.img, initrd.img and vmlinuz).
2. it never updates the `install_state` it always stays in `None` as our automation uses that value to monitor the installation progress it also fails Not sure how this one can be connected to wrsroot / sysadmin, if someone can point me a to a little further details of where this state change happens, I can take a look further into it. Maybe a permissions issue?
Sau!
3. Hacking those 2 issues I was able to complete deployment and execute Sanity (using config_controller --force) without significant problems (I saw some issues but are related to my host machine resources rather than the functionality)
Note: Issues 1 and 2 were not observed on any other ISOs recently validated.
Regards, José
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Wednesday, May 29, 2019 1:03 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews
Folks,
I pushed the rebased reviews for the username change to this set of 5 repos:
https://review.opendev.org/#/q/topic:wrsroot
I have created an ISO that the Intel team is testing with, if other members can build an iso with an updated manifest to include these changes and test.
Thanks Sau!
_______________________________________________ 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 5/29/19 4:32 PM, Penney, Don wrote:
The install_state progress notifications are part of the StarlingX installer customizations to Anaconda. If you have the stock CentOS installer, you won't get these notifications. Likewise, this would likely explain issue #1.
Yuppers, I have re-built my installer images and ISO, and seem to have fixed the eth interface issue and the install_state issue. I have run through the Setup/Provisioning and it's currently working on Sanity, but all passing green so far. I could log into the controller-1 with sysadmin and the correctly changed password so that control is working. Finally some positive news! Sau!
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Wednesday, May 29, 2019 7:11 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews
On 5/29/19 1:53 PM, Perez Carranza, Jose wrote:
Hi
I used the ISO provided by Saul and below are some findings on virtual environment.
1. Interfaces are named eth0 and eth1 instead of eth1000 and eth1001, this is breaking our automation flow I think this might be because I have an older installer, thoughts?
I am rebuilding the iso with updated installer files (squashfs.img, initrd.img and vmlinuz).
2. it never updates the `install_state` it always stays in `None` as our automation uses that value to monitor the installation progress it also fails Not sure how this one can be connected to wrsroot / sysadmin, if someone can point me a to a little further details of where this state change happens, I can take a look further into it. Maybe a permissions issue?
Sau!
3. Hacking those 2 issues I was able to complete deployment and execute Sanity (using config_controller --force) without significant problems (I saw some issues but are related to my host machine resources rather than the functionality)
Note: Issues 1 and 2 were not observed on any other ISOs recently validated.
Regards, José
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Wednesday, May 29, 2019 1:03 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews
Folks,
I pushed the rebased reviews for the username change to this set of 5 repos:
https://review.opendev.org/#/q/topic:wrsroot
I have created an ISO that the Intel team is testing with, if other members can build an iso with an updated manifest to include these changes and test.
Thanks Sau!
_______________________________________________ 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
I did another push of the sysadmin changes with clean'ed up Commit messages, removed [WIP] and fixed the groupname and long lines. Please do a review and any additional testing. I also changed the topic to be "sysadmin" instead of wrsroot! https://review.opendev.org/#/q/topic:sysadmin+(status:open+OR+status:merged) Thanks Sau! On 5/29/19 9:34 PM, Saul Wold wrote:
On 5/29/19 4:32 PM, Penney, Don wrote:
The install_state progress notifications are part of the StarlingX installer customizations to Anaconda. If you have the stock CentOS installer, you won't get these notifications. Likewise, this would likely explain issue #1.
Yuppers, I have re-built my installer images and ISO, and seem to have fixed the eth interface issue and the install_state issue.
I have run through the Setup/Provisioning and it's currently working on Sanity, but all passing green so far.
I could log into the controller-1 with sysadmin and the correctly changed password so that control is working.
Finally some positive news!
Sau!
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Wednesday, May 29, 2019 7:11 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews
On 5/29/19 1:53 PM, Perez Carranza, Jose wrote:
Hi
I used the ISO provided by Saul and below are some findings on virtual environment.
1. Interfaces are named eth0 and eth1 instead of eth1000 and eth1001, this is breaking our automation flow I think this might be because I have an older installer, thoughts?
I am rebuilding the iso with updated installer files (squashfs.img, initrd.img and vmlinuz).
2. it never updates the `install_state` it always stays in `None` as our automation uses that value to monitor the installation progress it also fails Not sure how this one can be connected to wrsroot / sysadmin, if someone can point me a to a little further details of where this state change happens, I can take a look further into it. Maybe a permissions issue?
Sau!
3. Hacking those 2 issues I was able to complete deployment and execute Sanity (using config_controller --force) without significant problems (I saw some issues but are related to my host machine resources rather than the functionality)
Note: Issues 1 and 2 were not observed on any other ISOs recently validated.
Regards, José
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Wednesday, May 29, 2019 1:03 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews
Folks,
I pushed the rebased reviews for the username change to this set of 5 repos:
https://review.opendev.org/#/q/topic:wrsroot
I have created an ISO that the Intel team is testing with, if other members can build an iso with an updated manifest to include these changes and test.
Thanks Sau!
_______________________________________________ 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
Hi Saul, As I indicated in the community meeting yesterday, we will have to see how this change impacts automation. We will need to modify automation according to this change. I will be able to start testing it in the later half of next week and it will take approximately 1 week to fully test and make required changes. Please don't merge these changes until the testing is complete. I expect to finish testing by Jun 12, 2019. Scott, I will need a build with Saul's changes next week. Can you please plan it in your schedule. Thanks. Numan -----Original Message----- From: Saul Wold <sgw@linux.intel.com> Sent: May-30-19 11:19 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews I did another push of the sysadmin changes with clean'ed up Commit messages, removed [WIP] and fixed the groupname and long lines. Please do a review and any additional testing. I also changed the topic to be "sysadmin" instead of wrsroot! https://review.opendev.org/#/q/topic:sysadmin+(status:open+OR+status:merged) Thanks Sau! On 5/29/19 9:34 PM, Saul Wold wrote:
On 5/29/19 4:32 PM, Penney, Don wrote:
The install_state progress notifications are part of the StarlingX installer customizations to Anaconda. If you have the stock CentOS installer, you won't get these notifications. Likewise, this would likely explain issue #1.
Yuppers, I have re-built my installer images and ISO, and seem to have fixed the eth interface issue and the install_state issue.
I have run through the Setup/Provisioning and it's currently working on Sanity, but all passing green so far.
I could log into the controller-1 with sysadmin and the correctly changed password so that control is working.
Finally some positive news!
Sau!
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Wednesday, May 29, 2019 7:11 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews
On 5/29/19 1:53 PM, Perez Carranza, Jose wrote:
Hi
I used the ISO provided by Saul and below are some findings on virtual environment.
1. Interfaces are named eth0 and eth1 instead of eth1000 and eth1001, this is breaking our automation flow I think this might be because I have an older installer, thoughts?
I am rebuilding the iso with updated installer files (squashfs.img, initrd.img and vmlinuz).
2. it never updates the `install_state` it always stays in `None` as our automation uses that value to monitor the installation progress it also fails Not sure how this one can be connected to wrsroot / sysadmin, if someone can point me a to a little further details of where this state change happens, I can take a look further into it. Maybe a permissions issue?
Sau!
3. Hacking those 2 issues I was able to complete deployment and execute Sanity (using config_controller --force) without significant problems (I saw some issues but are related to my host machine resources rather than the functionality)
Note: Issues 1 and 2 were not observed on any other ISOs recently validated.
Regards, José
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Wednesday, May 29, 2019 1:03 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews
Folks,
I pushed the rebased reviews for the username change to this set of 5 repos:
https://review.opendev.org/#/q/topic:wrsroot
I have created an ISO that the Intel team is testing with, if other members can build an iso with an updated manifest to include these changes and test.
Thanks Sau!
_______________________________________________ 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
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Saul / Numan In our case the impact of the changes is minimum, the automation suite works with a variable on a configuration file for the username and this variable is recognized by the entire automation system, hence we only have to update that variable with the new value, we ran some tests yesterday and did not faced any issues related to the username. Regards, José
-----Original Message----- From: Waheed, Numan [mailto:Numan.Waheed@windriver.com] Sent: Thursday, May 30, 2019 11:21 AM To: Saul Wold <sgw@linux.intel.com>; starlingx-discuss@lists.starlingx.io; Little, Scott <Scott.Little@windriver.com> Subject: Re: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews
Hi Saul,
As I indicated in the community meeting yesterday, we will have to see how this change impacts automation. We will need to modify automation according to this change.
I will be able to start testing it in the later half of next week and it will take approximately 1 week to fully test and make required changes. Please don't merge these changes until the testing is complete. I expect to finish testing by Jun 12, 2019.
Scott, I will need a build with Saul's changes next week. Can you please plan it in your schedule. Thanks.
Numan
-----Original Message----- From: Saul Wold <sgw@linux.intel.com> Sent: May-30-19 11:19 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews
I did another push of the sysadmin changes with clean'ed up Commit messages, removed [WIP] and fixed the groupname and long lines.
Please do a review and any additional testing.
I also changed the topic to be "sysadmin" instead of wrsroot! https://review.opendev.org/#/q/topic:sysadmin+(status:open+OR+status:merg ed)
Thanks Sau!
On 5/29/19 9:34 PM, Saul Wold wrote:
On 5/29/19 4:32 PM, Penney, Don wrote:
The install_state progress notifications are part of the StarlingX installer customizations to Anaconda. If you have the stock CentOS installer, you won't get these notifications. Likewise, this would likely explain issue #1.
Yuppers, I have re-built my installer images and ISO, and seem to have fixed the eth interface issue and the install_state issue.
I have run through the Setup/Provisioning and it's currently working on Sanity, but all passing green so far.
I could log into the controller-1 with sysadmin and the correctly changed password so that control is working.
Finally some positive news!
Sau!
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Wednesday, May 29, 2019 7:11 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews
On 5/29/19 1:53 PM, Perez Carranza, Jose wrote:
Hi
I used the ISO provided by Saul and below are some findings on virtual environment.
1. Interfaces are named eth0 and eth1 instead of eth1000 and eth1001, this is breaking our automation flow I think this might be because I have an older installer, thoughts?
I am rebuilding the iso with updated installer files (squashfs.img, initrd.img and vmlinuz).
2. it never updates the `install_state` it always stays in `None` as our automation uses that value to monitor the installation progress it also fails Not sure how this one can be connected to wrsroot / sysadmin, if someone can point me a to a little further details of where this state change happens, I can take a look further into it. Maybe a permissions issue?
Sau!
3. Hacking those 2 issues I was able to complete deployment and execute Sanity (using config_controller --force) without significant problems (I saw some issues but are related to my host machine resources rather than the functionality)
Note: Issues 1 and 2 were not observed on any other ISOs recently validated.
Regards, José
-----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Wednesday, May 29, 2019 1:03 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] wrsroot -> sysadmin rebased reviews
Folks,
I pushed the rebased reviews for the username change to this set of 5 repos:
https://review.opendev.org/#/q/topic:wrsroot
I have created an ISO that the Intel team is testing with, if other members can build an iso with an updated manifest to include these changes and test.
Thanks Sau!
_______________________________________________ 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
_______________________________________________ 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 (4)
-
Penney, Don
-
Perez Carranza, Jose
-
Saul Wold
-
Waheed, Numan