September 2018 - Starlingx-discuss

[Starlingx-discuss] CentOS 7.5 Upgrade - branch rebase
by Dean Troyer 17 Sep '18

17 Sep '18

I have rebased the f/centos75 branches to current master (as of 30-60 minutes before I typed this) in stx-integ, stx-root, stx-tools and stx-upstream. The merge commits need to be approved in Gerrit: https://review.openstack.org/#/q/topic:%22rebase+f/centos75%22 Note that stx-root has two due to an error on my part in initally creating the branch. I fixed the name and will keep the branch that Shuicheng is using in sync with the correct branch. dt -- Dean Troyer dtroyer(a)gmail.com

2 1

[Starlingx-discuss] download_mirror.sh error - bad repo?
by Penney, Don 17 Sep '18

17 Sep '18

Hi folks, I'm running download_mirror.sh as per the README (build a docker image, run download_mirror.sh in a container), but it fails in the first stage: failure: repodata/0fa206724f7262cecd5a4832731024dbff9b2cce3d64676fff1038bf08222c03-primary.xml.gz from Starlingx-mirrors.isu.net.sa_pub_fedora_fedora-epel_7Server_x86_64: [Errno 256] No more mirrors to try. http://mirrors.isu.net.sa/pub/fedora/fedora-epel/7Server/x86_64/repodata/0f…: [Errno 14] HTTP Error 404 - Not Found ERROR: Something wrong with downloading files listed in ./rpms_3rdparties.lst. Please check the log at /localdisk/logs/rpms_3rdparties_download_L1.log ! The repomd.xml file for this repo is pointing to non-existent files, and has a timestamp of Sept 11, 2018. Has this been broken since then? I was able to disable this repo in yum.repos.d and verify the pkgs I'm trying to add to the lst file are downloaded, but this issue would likely mean they won't get downloaded otherwise and would be unusable in the build until its resolved. Is anyone else seeing this error? Thanks, Don. Don Penney, Developer, Wind River

1 0

[Starlingx-discuss] py-bcrypt conflicts with python2-bcrypt
by Shang, Dehao 15 Sep '18

15 Sep '18

Hi: Based on ceph13.2.0 binary package, now i am re-building python-cephclient. At building python-cephclient process, lack some packages. The most packages can be resolved by manually adding new packages. But for py_bcrypt, I can't resolve package confilect between python2-bcrypt and py-bcrypt. == More details process == Based on ceph13.2.0 binary packages, "build-pkgs python-cephclient" will show some error. The most can be manually resolved, but one error is as following: Error: Package: 2:ceph-mgr-13.2.0-0.el7.centos.x86_64 (1270018088_localdisk_loadbuild_dehao_starlingx_std_results_dehaostarlingxtisr5pikestd_) 01:51:09 Requires: py-bcrypt 01:51:09 You could try using --skip-broken to work around the problem 01:51:09 You could try running: rpm -Va --nofiles --nodigest check ceph-mgr-13.2.0-0.el7.centos.x86_64.rpm, and verify this deps. [dehao@9f9456a3d92b RPMS]$ rpm -qp --requires ceph-mgr-13.2.0-0.el7.centos.x86_64.rpm | grep py_bcrypt. py_bcrypt so, when I manually download and add this packages, can successfully build python-cephclient. Next step, when run "build-iso", the conflict between py-bcrypt with python-bcrypt will occur as the below: 02:38:55 02:38:57 Warning: Infinite loop detected in dependency resolution. See /localdisk/loadbuild/dehao/starlingx/export/deps.txt for details -- exiting 02:38:57 These RPMS had problems (likely version conflicts) 02:38:57 py-bcrypt conflicts with python2-bcrypt-3.1.2-3.el7.x86_64 02:38:57 Could not install dependencies I look up some materials, and find this is a bug, namely it's not possible to simultaneously install python-bcrybt and py-bcrybt packages dependent. Conflict bug: https://bugzilla.redhat.com/show_bug.cgi?id=1473018 I also check my building environments, and verify that these two packages simultaneously exist. [root_cluster4: x86_64]# rpm -qp --provides python2-bcrypt-3.1.2-3.el7.x86_64.rpm < ----------------------- other project need this package. python-bcrypt = 3.1.2-3.el7 python2-bcrypt = 3.1.2-3.el7 python2-bcrypt(x86-64) = 3.1.2-3.el7 [root_cluster4: x86_64]# rpm -qp --provides py-bcrypt-0.4-4.el7.x86_64.rpm < --------------------------- the ceph-mgr package of ceph 13.2.0 require this packages py-bcrypt = 0.4-4.el7 py-bcrypt(x86-64) = 0.4-4.el7 can anyone tell me how I can solve this problem. Thanks Dehao

1 0

[Starlingx-discuss] Project call agenda open..
by Jones, Bruce E 15 Sep '18

15 Sep '18

The agenda for our next project call is open. Please feel free to add items to be discussed. https://etherpad.openstack.org/p/stx-status Agenda and Notes for the Sep 19th call * PTG Update * Review comments on the draft Feature Dev process (Bruce) * Review comments on the Governance draft (Bruce) * New Multi-OS sub-project (Bruce) * Containerized Services update (Brent) * Project de-coupling update (Brent) * Investing in StoryBoard development (Bruce) * Edge WG Update / slides (Greg) * Release status (Ghada) * Status from other teams / issues * Help needed?

1 0

[Starlingx-discuss] [Docs] RFC: Draft Feature Dev process
by Jones, Bruce E 14 Sep '18

14 Sep '18

We held a review of an early draft of a Feature Development process at the PTG this week, and I've written up an updated version thanks to the group feedback. It's out on the wiki at https://wiki.openstack.org/wiki/StarlingX/Feature_Development_Process. I am looking for any and all feedback on the document and the process it describes. brucej

1 0

[Starlingx-discuss] [build][meetings] Build team meetup Agenda for sept 17th 2018
by Lara, Cesar 14 Sep '18

14 Sep '18

Agenda -Scoping and planning for first release of sxtb tool (all) -Installer consolidation for starling X https://bugs.launchpad.net/starlingx/+bug/1790213 -opens Regards Cesar Lara Software Engineering Manager OpenSource Technology Center

1 0

[Starlingx-discuss] [Build] Feedback on stxb demo
by McKenna, Jason 14 Sep '18

14 Sep '18

Hi build team, Many thanks for the demo today, I think we're on the right track. As promised, here are a few feedback points on the demo, from the perspective of a developer: - I really like how the creation of the docker image is streamlined. - The system as currently demo'd as two copies of the repos. One in /(developers_path)/, and a second in /(developers_path)/stx-tools/(docker_image_root_dir)/localdisk/designer/builder/starlingx/. There should only one repo downloaded. o As a related point, a developer working on changes to a file would expect to make their changes to the repo in /(developers_path)/, rather than to the version in the docker image's filesystem. If I edited a puppet manifest (for example) /(developers_path)/cgcs-root/stx/stx-config/.../ then I would expect the build command to detect and use my changes if I do a build. - I'm a bit confused on the syntax regarding specifying and using localized mirrors, specifically with the -n and -p options. Would you provide examples of what commands I'd execute for use cases 1 and 2 below? I'm pretty sure these usages are supported, but am just seeking clarification. - Very happy do see it down to 1 docker image, rather than 2 :) - Native build - Being able to build in a docker image is great, but the would ideally be an option to perform a native build, rather than have to use a container - Minor nit - logs should be in a user directory (like $MY_REPO_ROOT_DIR/logs/) rather than in /var/log, as a non-privileged user wouldn't be able to log to /var/log. - Question - what privileges are required to create the docker image? Does the script assume the user has sudo privileges? - I'm unclear on what would happen with use cases 3-5 below. Have these types of uses been considered yet? Thanks again for the demo, -Jason Use Case 1: I am an organization with a site who is working with StarlingX. I want to provide a local mirror for my employees to use so they don't have to download all artifacts from the external internet every time. I want to create an automated job which I will run daily to download all artifacts from the Internet (if they do not already exist) and place them in directory /export/mirrors/starlingx. Assume the user running the automated job has permissions to write to /export/mirrors/starlingx Use Case 2: I am a developer within an organization which has a local mirror of artifacts available in /import/mirrors/starlingx. I want to build a StarlingX ISO without downloading rpms or src.rpms from the external internet. Use Case 3A: After doing a build, I just performed a repo sync, and the .lst files were not updated. If I perform another build of the ISO, will the system attempt to redownload external artifacts, even though nothing has changed? Use Case 3B: After doing a build, I just performed a repo sync, and noticed that the .lst files have been updated. If I perform another build of the ISO, will the stale mirror content be detected and the new additions downloaded (while not re-downloading anything which has not changed)? Use Case 4: I have manually made a change to a puppet manifest in sysinv (stx-config git) but want to test before I commit anything. How can I build a new ISO with my changes incorporated? Use Case 5: I want to test StarlingX with my own additional program (foobar.x86_64.rpm) on the ISO. How would I perform a build with this file added?

7 8

[Starlingx-discuss] Build Meeting Agenda Item for Monday, Sept 17th
by Young, Ken 14 Sep '18

14 Sep '18

Cesar / Sual, On Monday, I would like to discuss where we are with the installer for StarlingX. The following launchpad: https://bugs.launchpad.net/starlingx/+bug/1790213 revealed that Intel and Wind River are using different installers. I suspect that a general designer may be using a third installer. We need to get this down to 1 so when issues are reported, we are comparing apples to apples. I would like to quantify this problem and based upon interest, drive to a solution. Regards, Ken Y

1 0

Re: [Starlingx-discuss] [ Test ] Sanity results - summary posted
by Young, Ken 14 Sep '18

14 Sep '18

Erich, A couple of data points on our side. For our builds, we are using stock CentOS installer for 7.4. These are unchanged and we have not seen this issue on our side. Have you isolated when you made the changes to the installer? Is it the same time you started seeing this error? Does it make sense to revert to the stock installer while we get to the bottom of this issue to continue sanity? Regards, Ken Y On 2018-09-11, 8:30 PM, "Cordoba Malibran, Erich" <erich.cordoba.malibran(a)intel.com> wrote: I have narrowed down a little bit the issue, these are my findings. - I compared the bootimage_michel.iso with the stx-2018-09-11- 111.iso, which is today's ISO. - The are not significant package differences between them, minor versions has changed in some packages. - The issue is that once the kernel has been loaded through PXE, anaconda is unable to find python2-qpid package. Not sure if this is the first package that is requested. - From the anaconda shell I can see the http://pxecontroller/ serving the files and the repodata seems to be updated there. I installed yum manually and I was able to install python2-qpid package, (and any other available). - The content of the pxe-network-installer package is not the same, WR squashfs.img file has the kernel 3.10.0-693.2.2 but ours has 3.10.0- 862.6.3. We regenerate those files when the kernel was upgraded. (maybe this matches with the date where the issue started to arise..) So, my guess now is that the problem could be caused by the pxe- network-installer package. We create those files with the update- network-installer script. That's the same used in WR to generate these files? I'll keep diging in the generation of these files to see if there is any problem. -Erich On Tue, 2018-09-11 at 20:03 +0000, Lara, Cesar wrote: > I just wanted to make sure that we are able to reproduce the issue > regardless of the build environment. > > AFAIK CentOS 7.5 upgrade is a different issue/thread, but at the end > we can fine tune a process in which we are in the same conditions to > be able to replicate errors in any given build environment. > > Regards > Cesar Lara > > > -----Original Message----- > From: McKenna, Jason [mailto:Jason.McKenna@windriver.com] > Sent: Tuesday, September 11, 2018 2:02 PM > To: Lara, Cesar <cesar.lara(a)intel.com>; Alonso, Juan Carlos <juan.car > los.alonso(a)intel.com>; Khalil, Ghada <Ghada.Khalil(a)windriver.com>; > Martinez Monroy, Elio <elio.martinez.monroy(a)intel.com>; Jones, Bruce > E <bruce.e.jones(a)intel.com>; Cabrales, Ada <ada.cabrales(a)intel.com>; > starlingx-discuss(a)lists.starlingx.io; Thebeau, Michel <Michel.Thebeau > @windriver.com>; Young, Ken <Ken.Young(a)windriver.com>; Little, Scott > <Scott.Little(a)windriver.com> > Subject: RE: [ Test ] Sanity results - summary posted > > Hi Cesar, > > Would you elaborate on what differences you'd expect to see in an > empty mirror populated by the download tool, compared to an existing > mirror which was updated by the download tool? > > The mirror tools were written specifically to contain multiple > versions of packages. The build environment population tools take > the .lst file you have checked out, and places that version from the > mirror into your local environment guaranteeing that your build env > matches the .lst file. If your mirror contains versions 1.0.0, > 1.2.3, and 2.0.0 of a given package, then your environment will only > use the version called out in the .lst file you have checked out. > > This allows the same mirror to be used for multiple branches, for > multiple releases, for multiple development environments, etc, and > guarantees that a build can be reproduced down the road even if the > build inputs disappear from the Internet at some point in the > future. As long as all the artifacts named in the .lst file have > been downloaded at some point in the past, the build environment > produced from a fresh mirror vs a continually updated mirror will be > identical. > > The issue we are observing with the CentOS 7.5 update is that the > versions of packages called out in the .lst files for the centos75 > branch of stx-tools do not match the versions of packages called out > in centos75 branch of the other repos, like stx-integ. The other > branches are attempting to patch a (new) version of the source code, > but the .lst file is only bringing in (or downloading) and older > version of the source. > > -Jason > > > -----Original Message----- > > From: Lara, Cesar <cesar.lara(a)intel.com> > > Sent: September 11, 2018 1:44 PM > > To: Alonso, Juan Carlos <juan.carlos.alonso(a)intel.com>; Khalil, > > Ghada > > <Ghada.Khalil(a)windriver.com>; Martinez Monroy, Elio > > <elio.martinez.monroy(a)intel.com>; Jones, Bruce E > > <bruce.e.jones(a)intel.com>; Cabrales, Ada <ada.cabrales(a)intel.com>; > > starlingx-discuss(a)lists.starlingx.io; Thebeau, Michel > > <Michel.Thebeau(a)windriver.com> > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi all, > > > > Just wanted to point out that, to be able to reproduce the issues > > from > > Intel's ISO, somebody will need to go and create a build > > environment > > from scratch, using external upstream repositories to generate a > > new > > mirror, just the way we are doing it in our environment. Failing to > > do > > this will result in a apples to oranges comparison. > > > > Regards > > Cesar Lara > > > > -----Original Message----- > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso@intel.com] > > Sent: Tuesday, September 11, 2018 10:54 AM > > To: Khalil, Ghada <Ghada.Khalil(a)windriver.com>; Martinez Monroy, > > Elio > > <elio.martinez.monroy(a)intel.com>; Jones, Bruce E > > <bruce.e.jones(a)intel.com>; Cabrales, Ada <ada.cabrales(a)intel.com>; > > starlingx-discuss(a)lists.starlingx.io; Thebeau, Michel > > <Michel.Thebeau(a)windriver.com> > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi Ghada, > > > > Yes, before shared our ISOs I followed such steps and got the same > > issues. > > > > As I mention in the issue > > (https://bugs.launchpad.net/starlingx/+bug/1790213) I could get > > the > > ISO from Michel and testes in our infrastructure, issues not found. > > I > > guess there are differences between the way an ISO is built by > > Intel > > and Wind River since Intel got issues but Wind River does not. I > > think we should sync about this. > > > > Besides, our test infrastructure uses other commands to generate > > VMs, > > add/install hosts (controllers and computes), such commands was > > gotten > > from "tic_vb" repo, such repo was given by China team, if I am not > > wrong such repo was based on Wind River documentation; our test > > framework is based on "tic_vb". Anyway both ways got the same > > results. > > > > Regards. > > Juan Carlos Alonso > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil@windriver.com] > > Sent: Tuesday, September 11, 2018 8:53 AM > > To: Alonso, Juan Carlos <juan.carlos.alonso(a)intel.com>; Martinez > > Monroy, Elio <elio.martinez.monroy(a)intel.com>; Jones, Bruce E > > <bruce.e.jones(a)intel.com>; Cabrales, Ada <ada.cabrales(a)intel.com>; > > starlingx-discuss(a)lists.starlingx.io; Thebeau, Michel > > <Michel.Thebeau(a)windriver.com> > > Subject: RE: [ Test ] Sanity results - summary posted > > > > Hello Juan, > > I read the notes in the Launchpad. > > > > And, just to confirm, are you following the instructions under: > > https://wiki.openstack.org/wiki/StarlingX/Installation_Guide_Virtua > > l_E > > nviro > > nment/Controller_Storage > > and still reproducing the two issues below? > > > > I was not able to definitively tell from the Launchpad notes. It's > > important that both our teams are comparing apples to apples. > > > > Thanks, > > Ghada > > > > -----Original Message----- > > From: Alonso, Juan Carlos [mailto:juan.carlos.alonso@intel.com] > > Sent: Monday, September 10, 2018 1:50 PM > > To: Khalil, Ghada; Martinez Monroy, Elio; Jones, Bruce E; > > Cabrales, > > Ada; starlingx-discuss(a)lists.starlingx.io; Thebeau, Michel > > Subject: RE: [ Test ] Sanity results - summary posted > > > > Hi, > > > > Such launchpads were updated. > > > > A VM was set to upload the ISO tx-2018-08-28-88.iso, such ISO > > present > > two issues. Michael will upload his ISO, then we will re test > > witch > > each iso in our environment. > > > > An script is being developed to get the differences between ISOs. > > > > Regards. > > Juan Carlos Alonso > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil@windriver.com] > > Sent: Friday, September 7, 2018 4:43 PM > > To: Khalil, Ghada <Ghada.Khalil(a)windriver.com>; Martinez Monroy, > > Elio > > <elio.martinez.monroy(a)intel.com>; Jones, Bruce E > > <bruce.e.jones(a)intel.com>; Cabrales, Ada <ada.cabrales(a)intel.com>; > > starlingx-discuss(a)lists.starlingx.io; Thebeau, Michel > > <Michel.Thebeau(a)windriver.com> > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hi Elio/Ada, > > Are there any updates from your side on these two Launchpads? > > https://bugs.launchpad.net/starlingx/+bug/1790213 > > https://bugs.launchpad.net/starlingx/+bug/1790716 > > > > Michel Thebeau (Wind River) has been trying to reproduce these two > > issues (following the starlingx wikis) without success for two > > days > > now. He has been adding his findings to the bugs and communicating > > with your team. > > As a result of his investigation, he will be pushing some small > > fixes > > to stx- tools shortly (some cleanup). > > > > Please let us know if you need any further help from us. > > > > Thanks, > > Ghada > > > > -----Original Message----- > > From: Khalil, Ghada [mailto:Ghada.Khalil@windriver.com] > > Sent: Wednesday, September 05, 2018 5:39 PM > > To: Martinez Monroy, Elio; Jones, Bruce E; Cabrales, Ada; > > starlingx- > > discuss(a)lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Please see inline. There are notes in all the launchpads as well. > > > > I have tagged the last bug for the October release. The rest need > > more > > information to determine whether they gate or not: two maybe > > procedural and one requires more information. > > > > -----Original Message----- > > From: Martinez Monroy, Elio [mailto:elio.martinez.monroy@intel.com] > > Sent: Wednesday, September 05, 2018 2:23 PM > > To: Jones, Bruce E; Cabrales, Ada; > > starlingx-discuss(a)lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > My opinion below > > > > -----Original Message----- > > From: Jones, Bruce E [mailto:bruce.e.jones@intel.com] > > Sent: Wednesday, September 5, 2018 12:56 PM > > To: Cabrales, Ada <ada.cabrales(a)intel.com>; starlingx- > > discuss(a)lists.starlingx.io > > Subject: Re: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Should the bugs coming out of this be tagged/fixed for the October > > release? > > > > Related bugs: > > https://bugs.launchpad.net/starlingx/+bug/1790213 < --- Must, this > > bug > > is related with 2nd controller provisioning [[GK]] Using the > > instructions published on the wiki, our designer was not able to > > reproduce this issue. > > What instructions are the test team using? > > > > https://bugs.launchpad.net/starlingx/+bug/1790514 < --- Can wait > > until > > other issues are solved, will fail some test cases related to SSH > > [[GK]] Requested more information. This cannot be debugged further > > without this information. > > > > https://bugs.launchpad.net/starlingx/+bug/1790716 < --- Must, all > > instances need at least one compute for multimode [[GK]] Using the > > instructions published on the wiki, our designer was not able to > > reproduce this issue. The test team points to internal > > instructions > > which we have no access to. The supported install recipes need to > > be > > on the wiki. I think it is an invalid bug > > > > https://bugs.launchpad.net/starlingx/+bug/1790718 < --- Can wait > > since > > is related to FM , test cases will fail [[GK]] As Brent pointed > > out, > > this is dependent on the integration of stx-gui which is in > > progress. > > > > -----Original Message----- > > From: Cabrales, Ada [mailto:ada.cabrales@intel.com] > > Sent: Wednesday, September 5, 2018 10:50 AM > > To: starlingx-discuss(a)lists.starlingx.io > > Subject: [Starlingx-discuss] [ Test ] Sanity results - summary > > posted > > > > Hello all, > > > > As mentioned on the project meeting today, we're posting the > > summary of the sanity test runs on the Test wiki [0]. The sanity > > is > > triggered each time an ISO is generated (a daily task). > > > > Right now we are posting the results manually, and working on a > > way > > for automating it. Logs of the run are not included, if you want > > to > > have them, you can contact Elio to get them sent to you. > > > > > > [0] > > https://wiki.openstack.org/wiki/StarlingX/Test#Latest_ISO_image_San > > ity > > _S > > ummary > > > > Regards > > Ada > > > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss(a)lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss(a)lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss(a)lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss(a)lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss(a)lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss(a)lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss(a)lists.starlingx.io > > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus > > s > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss(a)lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

4 6

Re: [Starlingx-discuss] interface and network configuration changes are merged
by Ho, Teresa 13 Sep '18

13 Sep '18

The commits for the Story https://storyboard.openstack.org/#!/story/2003087 have been merged. Teresa Ho From: Ho, Teresa Sent: Sunday, September 09, 2018 11:31 PM To: starlingx-discuss(a)lists.starlingx.io Subject: Heads up: interface and network configuration changes This is to inform you that the upcoming feature story "Generalized interface and network configuration" will impact system setup. A review will be posted shortly. For more background information, please refer to the Story: https://storyboard.openstack.org/#!/story/2003087 The following describes the user interface changes for interface and network configuration. * Network CLI commands * The parameters mtu, link_capacity and vlan_id are removed from the network table * New network-add and network-delete usage: system network-add <network_name> <network type> <dynamic> <pool_uuid> Add a network. Positional arguments: <network_name> Name of network [REQUIRED] <network type> Type of network [REQUIRED] <dynamic> dynamic [REQUIRED] <pool_uuid> The uuid of the address pool [REQUIRED] usage: system network-delete <network_uuid> Delete a network Positional arguments: <network_uuid> UUID of network entry * Interface CLI commands * The new interface class parameter replaces the existing networktype parameter. usage: system host-if-add [-a <ae mode>] [-x <txhashpolicy>] [-V <vlan_id>] [-m <mtu>] [-c <class>] [--networks <network name or id>] [--ipv4-mode <ipv4_mode>] [--ipv6-mode <ipv6_mode>] [--ipv4-pool <ipv4 pool uuid or name>] [--ipv6-pool <ipv6 pool uuid or name>] <hostname or id> <interface name> [<iftype>] [<providernetworks>] <portsorifaces> [<portsorifaces> ...] Add an interface. Positional arguments: <hostname or id> Name or ID of host [REQUIRED] <interface name> Name of interface [REQUIRED] <iftype> Type of the interface <providernetworks> The provider network attached to the interface (default: None) [REQUIRED when interface class is data or pci-passthrough <portsorifaces> Name of port(s) or interface(s) [REQUIRED] Optional arguments: -a <ae mode>, --aemode <ae mode> The AE mode (balanced or active_standby or 802.3ad) -x <txhashpolicy>, --txhashpolicy <txhashpolicy> The balanced tx distribution hash policy -V <vlan_id>, --vlan_id <vlan_id> The VLAN id of the interface -m <mtu>, --imtu <mtu> The MTU of the interface -c <class>, --ifclass <class> The class of the interface --networks <network name or id> Name or ID of network --ipv4-mode <ipv4_mode> The IPv4 address mode of the interface --ipv6-mode <ipv6_mode> The IPv6 address mode of the interface --ipv4-pool <ipv4 pool uuid or name> The IPv4 address pool name or uuid if mode is set to 'pool' --ipv6-pool <ipv6 pool uuid or name> The IPv6 address pool name or uuid if mode is set to 'pool' usage: system host-if-modify [-n <new interface name>] [-m <mtu>] [-p <providernetworks>] [-a <ae mode>] [-x <txhashpolicy>] [-c <class>] [--networks <network name or id>] [--ipv4-mode <ipv4_mode>] [--ipv6-mode <ipv6_mode>] [--ipv4-pool <ipv4 pool uuid or name>] [--ipv6-pool <ipv6 pool uuid or name>] [-N <sriov numvfs>] <hostname or id> <interface name or uuid> Modify interface attributes. Positional arguments: <hostname or id> Name or ID of host [REQUIRED] <interface name or uuid> Name or UUID of interface [REQUIRED] Optional arguments: -n <new interface name>, --ifname <new interface name> The new name of the interface -m <mtu>, --imtu <mtu> The MTU of the interface -p <providernetworks>, --providernetworks <providernetworks> The provider network attached to the interface [REQUIRED] -a <ae mode>, --aemode <ae mode> The AE mode (balanced or active_standby or 802.3ad) -x <txhashpolicy>, --txhashpolicy <txhashpolicy> The balanced tx distribution hash policy -c <class>, --ifclass <class> The class of the interface --networks <network name or id> Name or ID of network --ipv4-mode <ipv4_mode> The IPv4 address mode of the interface --ipv6-mode <ipv6_mode> The IPv6 address mode of the interface --ipv4-pool <ipv4 pool uuid or name> The IPv4 address pool name or uuid if mode is set to 'pool' --ipv6-pool <ipv6 pool uuid or name> The IPv6 address pool name or uuid if mode is set to 'pool' -N <sriov numvfs>, --num-vfs <sriov numvfs> The number of SR-IOV VFs of the interface * Interface network associations Multiple networks can be assigned to an interface. usage: system interface-network-assign <hostname or id> <interface name or uuid> <network name or uuid> Assign a network to an interface. Positional arguments: <hostname or id> Name or ID of host [REQUIRED] <interface name or uuid> Name of interface [REQUIRED] <network name or uuid> Name of UUID of IP network [REQUIRED] usage: system interface-network-remove <interface network uuid> Remove an assigned network from an interface. Positional arguments: <interface network uuid> UUID of interface network entry Teresa Ho

1 0