January 2019 - Starlingx-discuss

[Starlingx-discuss] Starlingx network requirement
by Quick Convey 21 Jan '19

21 Jan '19

Dear All, I am planing to setup Starlingx in bare-metal (controller-storage deployment) https://docs.starlingx.io/installation_guide/controller_storage.html#contro… I have couple of questions *Q1)* What is the network requirements for this setup. All nodes should be in same network, that is the only requirement, right ? *Q2)* In "Hardware Requirements" section, I seen *"Data: n x 10GE Compute"*, what that means, is it number of physical interfaces needed for data ? what that* "n" *indicate ? is it number of compute nodes ? *Q3) *What is the number of physical interfaces needed in controller and compute bare-metal nodes ?. From the document I understand that only 2 physical interfaces are enough, right ? *Q4) *Is there any picture which shows *Management*, *OAM* and *Data* interface connections between controller and compute nodes ? *Thanks,*

2 5

[Starlingx-discuss] [Test] Minutes of Meeting - Test Breakout Session - Jan 16, 2019
by Waheed, Numan 19 Jan '19

19 Jan '19

Following are the notes from Test Breakout Session in Phoenix, AZ. Date: Jan 16, 2019 Participants: Numan, Ada, Victor, Frank * Test Repository o Test Repository will be setup before 2019.05 release. There will be all the content in the repository but it may not be all automated. o Jose from Ada's team will be the lead in setting up the repository. o There will be at least 2 cores for each sub-repo. o Same person can be nominated as Cores for more than one sub-repo. o List of cores will be provided by Jan 31, 2019 o Structure of Test Repository was discussed in length and Test repository will be setup according to the discussed structure. * Test Dashboard o Christopher from Ada's team is working on setting up test dashboard. o First step is to estimate the space required to host test dashboard. o Once the estimated space requirement is available, we will be requesting CENGN to host this dashboard. o Christopher will be maintaining the dashboard. o Linking the dashboard with automation FW to upload test results will be the responsibility of team using the automation FW. * Publically Available Test Environment o Dean indicated that there is publically accessible environment available for other projects by Intel. The proposal is to add required number of servers in the existing pool so that new permissions are not needed to access these servers. o Ada is going to follow up with Dean and Bruce about it. o There will be 4 configurations provided for public access (AIO-Simplex, AIO-Duplex, Multi-Node, Multi-Node with Dedicated Storage). o Setting up a scheduler and how the permissions will be granted is not decided at this point. It will be decided once the servers are available. * Sanity o Sanity test cases will change due to patch elimination and containerization. o Numan will provide the procedure for sanity test cases to community. o Ada's team is going to automate these test cases and provide the automated tests to community. * Regression (Manual / Automated) o Some features will not be available after Patch Elimination. o Test Case procedures will change for some features that are available in Stein Release. o Numan and Ada's team will collaborate to go through these test case suites and find out which test cases are obsolete and which test cases need changing. o These changes will be shared with community and the test cases will be uploaded to Test Repository. * Virtual Environment Installer o Numan and Ada's team will work together to create a Virtual Environment Installer for community. * Updating Test Wiki o Test Wiki needs updating o As the test cases are changing due to Patch Elimination and Containerization, Test Wiki needs updating. o Numan and Ada will work together to update the Wiki. o Wiki will be updated with information about Automation FrameWork. o Once Test Repository is available, a new section will be added to Test Wiki regarding Test Repository. o After creation of Test Dashboard, information regarding Test Dashboard will be added to test wiki. * Performance Testing o Victor will be leading the Performance testing. o What needs to be collected and different categories of performance testing suitable for STX were discussed in length at this meeting. o Victor will send his proposal regarding what he is planning to collect, performance test cases, which tools will be used and how the data will be used to the community for feedback. Numan.

1 0

[Starlingx-discuss] Bulk update of launchpad tags from stx.2019.03 to stx.2019.05
by Khalil, Ghada 19 Jan '19

19 Jan '19

Hello all, The next StarlingX release will be called stx.2019.05 (as confirmed in the F2F Chandler meeting earlier this week). The launchpad tags have been updated from stx.2019.03 to stx.2019.05. If you are subscribed to a launchpad, you'll likely get an email with the change (sorry about the spam). Moving forward, any issues gating the next StarlingX release will be tagged with stx.2019.05. Regards, Ghada PS: The same update will be done for StoryBoard shortly.

1 0

[Starlingx-discuss] [build-report] STX_build_docker_images - Build # 26 - Failure!
by build.starlingx＠gmail.com 19 Jan '19

19 Jan '19

Project: STX_build_docker_images Build #: 26 Status: Failure Timestamp: 20190118T201420Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/f/stein//20190118T172840Z… -------------------------------------------------------------------------------- Parameters BRANCH: f/stein MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-stein/20190118T172840Z OS: centos MUNGED_BRANCH: f-stein MY_REPO: /localdisk/designer/jenkins/f-stein/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/f/stein//20190118T172840Z… PUBLISH_LOGS_BASE: /export/mirror/starlingx/f/stein//20190118T172840Z/logs MY_REPO_ROOT: /localdisk/designer/jenkins/f-stein DOCKER_BUILD_ID: jenkins-f-stein-20190118T172840Z-builder OPENSTACK_RELEASE: master TIMESTAMP: 20190118T172840Z OS_VERSION: 7.5.1804 PUBLISH_INPUTS_BASE: /export/mirror/starlingx/f/stein//20190118T172840Z/inputs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/f/stein//20190118T172840Z/outputs

2 1

[Starlingx-discuss] Denver Summit discount codes and CFP reminder
by Ildiko Vancsa 19 Jan '19

19 Jan '19

Hi, In preparation to the upcoming Denver Open Infrastructure Summit, if you’ve had code merged into the StarlingX repos between July 11, 2018 through Jan 11, 2019, or serving in a leadership position (TSC, PL, TL) - then you should have received an email today with a discount code to register to attend the Summit and PTG. However, if you have already or are planning to (which I really hope you are) submit a talk to the Summit CFP, then please wait on registering until later in February when the accepted speaker notifications are sent out. If your talk is accepted, at that time you will receive a second discount code to apply with further instructions. Thanks to everyone who has contributed to StarlingX so far! We hope you will attend the Summit in Denver and make the most of the opportunity for open collaboration there! As a reminder to submit a talk to the CFP, the deadline is next Wednesday, Jan 23: https://www.openstack.org/summit/denver-2019/ Please let me know if you have any questions. Thanks and Best Regards, Ildikó

1 0

[Starlingx-discuss] [build-report] STX_build_stein_master - Build # 18 - Still Failing!
by build.starlingx＠gmail.com 19 Jan '19

19 Jan '19

Project: STX_build_stein_master Build #: 18 Status: Still Failing Timestamp: 20190118T172840Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/f/stein//20190118T172840Z… -------------------------------------------------------------------------------- Parameters BUILD_CONTAINERS: true

2 1

[Starlingx-discuss] [build-report] STX_publish - Build # 63 - Failure!
by build.starlingx＠gmail.com 19 Jan '19

19 Jan '19

Project: STX_publish Build #: 63 Status: Failure Timestamp: 20190118T193431Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/f/stein//20190118T172840Z… -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/f-stein/20190118T172840Z OS: centos PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/f/stein//20190118T172840Z… TIMESTAMP: 20190118T172840Z PUBLISH_INPUTS_BASE: /export/mirror/starlingx/f/stein//20190118T172840Z/inputs PUBLISH_LOGS_BASE: /export/mirror/starlingx/f/stein//20190118T172840Z/logs PUBLISH_OUTPUTS_BASE: /export/mirror/starlingx/f/stein//20190118T172840Z/outputs MY_REPO_ROOT: /localdisk/designer/jenkins/f-stein PUBLISH_DISTRO_BASE: /export/mirror/starlingx/f/stein/

2 1

[Starlingx-discuss] [tsc][election] Election process for StarlingX
by Ildiko Vancsa 19 Jan '19

19 Jan '19

Hi, As the first TSC election is scheduled for Q2 this year it is time to think about the details of the process. The OpenStack Foundation will provide help with the first elections with the end goal to reach a 100% community-owned election process. I would like to draw your attention to the wiki page describing the OpenStack election process which we can use as a basis for StarlingX as well: https://governance.openstack.org/election/ Please be aware of differences, such as StarlingX not requiring a Foundation membership to participate in the elections which needs to be reflected on the tooling side as well: https://docs.starlingx.io/governance/reference/tsc/stx_charter.html#electio… I created an etherpad in case the community would like to brainstorm before being ready to submit a patch in the governance repository to describe the process to use: https://etherpad.openstack.org/p/StarlingX_Election_Process Besides the etherpad we can use the TSC calls to discuss the topic further. Please let me know if you have any questions. Thanks and Best Regards, Ildikó

1 0

[Starlingx-discuss] Marketing planning call series starting in first week of February
by Ildiko Vancsa 19 Jan '19

19 Jan '19

Hi StarlingX Community, We had a planning meeting at the end of December where we were talking about community priorities and planning marketing and outreach activities. To pick up the discussion and keep the ball rolling we agreed to have the call as a series to make sure we are on the right track with both planning and execution. The next call is planned for __February 6 at 8am Pacific__. If you are planning to attend this meeting and are absolutely unable to make this slot please let me know. As finding a slot that works for everyone is nearly impossible please be flexible as much as possible. As a reminder here is the etherpad we used for the last call: https://etherpad.openstack.org/p/2019_StarlingX_Marketing_Plans Thanks and Best Regards, Ildikó

1 0

[Starlingx-discuss] Mailing list notes
by Dean Troyer 19 Jan '19

19 Jan '19

I just flushed the starlingx-discuss moderation queue, there were a number of messages from the last week or so stacked up along with a couple hundred spam emails (yay? we're well-known enough to attract spam? :) The top reasons most messages get caught in moderation are: 1) message too big - we have a limit of 60K on message size. I am aware that the majority of subscribers use a mail client that encourages top-posting and that leads to not trimming messages, in this environment that makes conversations over multiple messages hard to follow. Trimming unnecessary quoting in messages makes for a better record of conversations, and will ensure that you are not delayed by the size limit. 2) too many recipients - The list is configured to set Reply-to to the original poster and not the list itself, so many people hit reply-all to reply to the list. Again, some mail readers handle this poorly and It is good practice to trim the recipients when replying to a mailing list. 3) not subscribed - For whatever reason mailman (the list processor) doesn't think your email is subscribed and refuses to deliver. The size of the spam backlog is a testament to why we keep this on. We generally also allow these through as it is often new people to the community and they will get notified that they need to subscribe to the list. I am investigating a coupe of reports that messages are not being properly forwarded and the user is notified that they are not subscribed when they believe they are. If you think you are also having this problem let me know and I'll check it out. One is an anomaly, two is a coincidence, three, well at three we may have a pattern :) Also, you can verify your subscription settings at http://lists.starlingx.io/cgi-bin/mailman/options/starlingx-discuss dt -- Dean Troyer dtroyer(a)gmail.com

4 3