Re: [openstack-dev] Usage of @author tags in the header of Python files

On 08/10/2014 10:39, "Ihar Hrachyshka" wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA512 > >On 08/10/14 09:30, Christian Berendt wrote: >> After proposing a change to Horizon to remove the @author tags from >> the header of Python files >> (https://review.openstack.org/#/c/126656/) Matthi

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

I agree with Devananda's definition of Œhardware discovery¹ and other tools similar to Ironic use the term discovery in this way, however I have found that these other tools often bundle the gathering of the system properties together with the discovery of the hardware as a single step from a user

[openstack-dev] [ironic] [inspector] Auto discovery extension for Ironic Inspector

Auto discovery is a topic which has been discussed a few times in the past for Ironic, and its interesting to solve because its a bit of a chicken and egg problem. The ironic inspector allows us to inspect nodes that we don't know the mac addresses for yet, to do this we run a global DHCP PXE ru

[openstack-dev] [ironic] [inspector] [neutron] DHCP Options on Neutron networks

For the ironic inspector to be able to inspect nodes that we don't know the mac addresses for we have to run a DHCP rule that will respond to all mac addresses for PXE booting the inspector ramdisk. In order to provide this functionality right now we are running our own instance of dnsmasq, con

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

Openstack baremetal provision provide or -provide Just doesn't feel right to me, it feels like I am typing more that I need to and it feels like I'm telling it to do the same action twice. I would much rather see: Openstack baremetal provide UUID Openstack baremetal activate UUID Openstack bare

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

ions however if we want to cover support port/chassis/driver and more ironic resources, so how about below proposal? #openstack baremetal The resource/target can be one item in following list: node port chassis driver ... Make sense? On Tue, Nov 10, 2015 at 7:25 PM, Sam Betts (sambetts) ma

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

I think all the filtering etc that exists on the current CLI should move over to OSC, I personally find things like --fields super useful. +1 to removing "chassis show --nodes" and making it part of node list. +1 to deploy, instead of activate. Jim also suggested provision. WDYT? I'd only ch

Re: [openstack-dev] [ironic] [inspector] Auto discovery extension for Ironic Inspector

What Yuiko has described makes a lot of sense, and from that perspective perhaps instead of us defining what driver a node should and shouldn't be using a config file, we should just provide a guide to using the inspector rules for this and maybe some prewritten rules that can set the driver and

Re: [openstack-dev] [ironic] usage of ironic-lib

I personally disagree with saying that if we wanted it make it usable by projects other than ones in the Ironic umbrella it should go into oslo. I think that non-ironic projects directly related to Ironic such as out of tree drivers etc, should be able to utilise the code placed into ironic-lib.

Re: [openstack-dev] [ironic] versioning of IPA, it is time or is it?

I personally think that we need IPA versioning, but not so that we can pin a version. We need versioning so that we can do more intelligent graceful degradation in Ironic without just watching for errors and guessing if a feature isn’t available. If we add a new feature in Ironic that requires a

Re: [openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

On 07/06/2016 23:59, "Kris G. Lindgren" mailto:klindg...@godaddy.com>> wrote: Replying to a digest so sorry for the copy and pastes >> There's also been discussion of ways we could do ad-hoc changes in RAID >> level, >> based on flavor metadata, during the provisioning process (rather th

Re: [openstack-dev] [ironic] Proposing two new cores

Thanks everyone, I¹m super excited to continue my contribute to Ironic! Sam On 18/06/2016 16:25, "Jim Rollenhagen" wrote: >On Thu, Jun 16, 2016 at 11:12:31AM -0400, Jim Rollenhagen wrote: >> Hi all, >> >> I'd like to propose Jay Faulkner (JayF) and Sam Bet

[openstack-dev] [ironic] [ironic-python-agent] Broken functional tests

This patch https://review.openstack.org/#/c/324909/ merged last night and has broken the IPA functional tests. To verify pull master and run "tox -r -e func" and it¹ll fail to run. If you git checkout the commit before that one merged the same thing passes successfully. Seeing this error has mad

Re: [openstack-dev] [ironic] why do we need setting network driver per node?

My use case is supporting mixed hardware environments with hardware that has greater network capabilities and hardware without these capabilities without limiting my all my equipment to the lowest common feature set. The use case I’m describing will have some nodes configured with the neutron mu

Re: [openstack-dev] [ironic] UFCG OneView CI comments missing recheck command

On the official OpenStack Third Party CI Documentation, it is a requirement for third party Cis to respond to comments in the following formats: recheck recheck (Where is replaced with the name of your third party CI.) http://docs.openstack.org/infra/system-config/third_party.html#requireme

Re: [openstack-dev] [ironic] Dell recheck command issue (was: UFCG OneView CI comments missing recheck command)

Please can we not reinvent our own standard for this, as mentioned in the other thread on this topic, there is an OpenStack standard for third party CI recheck commands that can be found in the third party CI docs: http://docs.openstack.org/infra/system-config/third_party.html#requirements Thi

Re: [openstack-dev] [ironic] [inspector] Proposing Anton Arefiev (aarefiev) for ironic-inspector-core

+1 from me too :D Sam On 05/04/2016 17:45, "Jim Rollenhagen" wrote: >+1 from me :) > >// jim > >> On Apr 5, 2016, at 03:24, Dmitry Tantsur wrote: >> >> Hi! >> >> I'd like to propose Anton to the ironic-inspector core reviewers team. >>His stats are pretty nice [1], he's making meaningful

Re: [openstack-dev] [Ironic] Failed to update Neutron port

Looking at the errors here it appears that everything is configured correctly in Ironic (mac addresses etc) because you are getting through the ramdisk boot and deploy successfully. The error that is of real concern here is "Unauthorized: {"error": {"message": "The resource could not be found."

Re: [openstack-dev] [ironic] [inspector] Proposing Anton Arefiev (aarefiev) for ironic-inspector-core

Congrats Anton!!! Sam On 12/04/2016 10:52, "Dmitry Tantsur" wrote: >On 04/05/2016 12:24 PM, Dmitry Tantsur wrote: >> Hi! >> >> I'd like to propose Anton to the ironic-inspector core reviewers team. >> His stats are pretty nice [1], he's making meaningful reviews and he's >> pushing important t

Re: [openstack-dev] [ironic][nova][neutron][qa] Injecting code into grenade resource create phase

Its easy enough to setup devstack today to use a flat neutron network instead of faking it using the tenant networks which we don¹t support, I do it in my third party CI for real hardware, if we can make it work for fake BM VMs too would it solve this issue, or would grenade override that? For ref

Re: [openstack-dev] [Ironic] Let's talk about API versions

After reading through this thread as a whole, I¹d like to summarise my thoughts so far: * I've noticed all these discussions revolve around existing people using the API, and seem to ignore that most new users of the API don¹t care how it used to work, and just want the full feature set without h

Re: [openstack-dev] [Ironic] [Inspector] Addition to ironic-inspector-core: Sam Betts

Thanks everyone, proud to be on the team! Sam On 25/08/2015 12:32, "Lucas Alvares Gomes" wrote: >Congrats! Well deserved > >On Tue, Aug 25, 2015 at 12:24 PM, Yuiko Takada > wrote: >> Sam, congrats and welcome! >> >> >> Yuiko Takada >> >> 2015/08/25 19:53、Dmitry Tantsur のメッセージ: >> >>> Hi all! >

Re: [openstack-dev] [Ironic] Suggestion to split install guide

Looking at what they¹re building for Neutron, http://docs.openstack.org/networking-guide, they have a quite fine grain splitting of their guide with a large contents page that helps find things easily. My personal issues with the current ironic guide all comes down to navigation, the current Table

Re: [openstack-dev] [ironic] [tripleo] [stable] Phasing out old Ironic ramdisk and its gate jobs

My preference is option 4, however with a slight difference, and that is that we only apply the DIB cap to the job that¹s testing the bash ramdisk. We can say that the bash ramdisk is deprecated in liberty and will not be receiving any further updates, so we¹re capping the DIB version, but because

Re: [openstack-dev] [ironic] midcycle voice channel is 7777

is working for the Thursday midcycle session so we are moving back to that channel. Sam On 17/02/2016 15:19, "Jim Rollenhagen" wrote: >So, someone has injected their hold music into 7778. We've now moved to >7779, sorry for the trouble :( > >// jim > >On Wed, Feb 17, 2016 at 07:01:22AM -08

Re: [openstack-dev] [Ironic] Clarifications about ThirdParty CI deadlines

I'll try to answer your questions as best I can. As I understand it, "receive events" means that you can listen to the gerrit stream and take an action when for example a new patch is uploaded or a recheck comment is left etc. Initially we encourage people to get their CI listening to the ci-san

Re: [openstack-dev] [ironic] [tripleo] [dib] RFC: moving/transitioning the ironic-agent element to the ironic-python-agent tree

I would like to suggest that we create a new repo for housing the tools required to build ironic python agent images: ironic-python-agent-builder(tooling). This would include, the DIB element, the existing coreos and tinyipa methods and hopefully in the future the buildroot method for creating

Re: [openstack-dev] [ironic] Routed Networks, flat driver and physical network awareness

scheduling gives you a valid baremetal node when you request a baremetal instance on a routed network. Any help and/or reviews of this work would be most appreciated, Sam Betts (sambetts) On 28/06/2017, 10:31, "Harald Jensås" wrote: Hi, With the following Neutron patches recen

Re: [openstack-dev] [ironic] Looking for a good end-to-end demo of ironic integrated within openstack

Hey Greg, The Ironic deploy agent images are ramdisk images which include the ironic-python-agent https://docs.openstack.org/ironic-python-agent/latest/ Which is a tool build by the ironic team and used by ironic to deploy and cleanup the baremetal nodes. The cirros images are just the default

Re: [openstack-dev] [ironic] Looking for a good end-to-end demo of ironic integrated within openstack

d mechanism uses the ‘config drive’ to configure the bare metal server as desired by ironic ??? Greg. From: "Sam Betts (sambetts)" Reply-To: "openstack-dev@lists.openstack.org" Date: Monday, July 24, 2017 at 12:26 PM To: "openstack-dev@lists.openstack.org" Subje

Re: [openstack-dev] [ironic] [release] [stable] pike release

Quick reply with my thoughts in-line. Sam On 21/08/2017, 10:13, "Dmitry Tantsur" wrote: (adding the release and stable team just for their information) Thanks Julia and everyone for handling this situation while I was out. More comments inline. On 08/17/2017 07:13 PM,

Re: [openstack-dev] [ironic] Proposing Shivanand Tendulker for ironic-core

+1, Sam On 03/10/2017, 08:21, "tua...@vn.fujitsu.com" mailto:tua...@vn.fujitsu.com>> wrote: +1 , Yes, I definitely agree with you. Regards Tuan From: Nisha Agarwal [mailto:agarwalnisha1...@gmail.com] Sent: Tuesday, October 03, 2017 12:28 PM To: OpenStack Developm

Re: [openstack-dev] [ironic] How is the interface for tftpboot server typically configured on OVS ?

There are multiple options for doing this, but I suggest avoiding manually plumbing anything into OVS as it can lead to some nastiness in the future. My personal recommended way to do this is to create the provisioning network in neutron with a known VLAN and trunk it separately down to the iron

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

Quick update for third party CI owners, if you are using “DEVSTACK_GATE_TEMEPST_ALL_PLUGIN=1” in your CI you will need to disable that and use the TEMPEST_PLUGINS+= in your local config as described below to enable *only* the ironic-tempest-plugin. If you have …TEMPEST_ALL_PLUGIN=1 set it’ll lo

Re: [openstack-dev] [ironic] why do we need setting network driver per node?

Thanks for following up with this Devananda, I¹ve left a couple of corrections to my proposal inline, unfortunately IRC isn¹t the best for putting ideas this complex across :) Sam On 11/07/2016 21:57, "Devananda van der Veen" wrote: >We spent the majority of today's weekly IRC meeting [1] discu

Re: [openstack-dev] [ironic] How to handle defaults in driver composition reform?

There have been several discussions brought about by new interface types and how they fit into the existing driver composition spec. Network and Volume connector interfaces are examples of two interfaces who’s implementations can depend highly on the environment they are being used in, as well a

Re: [openstack-dev] [ironic][neutron][nova] Sync port state changes.

On 26/07/2016 09:32, "John Garbutt" wrote: >On 22 July 2016 at 11:51, Vasyl Saienko wrote: >> Kevin, thanks for reply, >> >> On Fri, Jul 22, 2016 at 11:50 AM, Kevin Benton wrote: >>> >>> Hi, >>> >>> Once you solve the issue of getting the baremetal ports to transition >>>to >>> the ACTIVE sta

[openstack-dev] [ironic][nova] Indivisible Resource Providers

While discussing the proposal to add resource_class' to Ironic nodes for interacting with the resource provider system in Nova with Jim on IRC, I voiced my concern about having a resource_class per node. My thoughts were that we could achieve the behaviour we require by every Ironic node resourc

[openstack-dev] [ironic] How should ironic and related project names be written?

Its official OpenStack policy that project names be written in lower case, for example Ironic must always be written as ironic, however I was recently writing a spec for IPA, and was unsure how to approach writing IPAs name in full. Discussing this with Dmitry on IRC, we decided it would be best

Re: [openstack-dev] [ironic] network_interface, defaults, and explicitness

On 01/08/2016 13:10, "Jim Rollenhagen" wrote: >Hey all, > >Our nova patch for networking[0] got stuck for a bit, because Nova needs >to know which network interface is in use for the node, in order to >properly set up the port. > >The code landed for network_interface follows the following order

Re: [openstack-dev] [ironic] Driver removal policies - should we make it softer?

On 19/08/2016 18:44, "Villalovos, John L" wrote: >> -Original Message- >> From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] >> Sent: Friday, August 19, 2016 7:15 AM >> To: OpenStack Development Mailing List (not for usage questions) >> >> Subject: [openstack-dev] [ironic] Driver rem

Re: [openstack-dev] [ironic] Nominating Hironori Shiina for ironic-core

+1 On 09/02/2018, 04:36, "Shivanand Tendulker" mailto:stendul...@gmail.com>> wrote: +1 On Wed, Feb 7, 2018 at 11:53 AM, John Villalovos mailto:openstack@sodarock.com>> wrote: +1 On Mon, Feb 5, 2018 at 10:12 AM, Julia Kreger mailto:juliaashleykre...@gmail.com>> wrote: I would like to nomi

Re: [openstack-dev] [ironic] Monthly bug day?

100% on board with this, I think it was really productive! Sam On 23/04/2018, 15:44, "Jim Rollenhagen" mailto:j...@jimrollenhagen.com>> wrote: On Mon, Apr 23, 2018 at 8:04 AM, Michael Turek mailto:mjtu...@linux.vnet.ibm.com>> wrote: Hey everyone! We had a bug day about two weeks ago and it we

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

There are a couple of reasons we want to become an official OpenStack project. From a project perspective, we want to be recognized that the project isn’t just a “public source” repo for Cisco’s drivers but is a community driven open source project for supporting Cisco hardware/software and we w

Re: [openstack-dev] [ironic] New mascot design

+100 On 06/02/2017, 12:32, "Dmitry Tantsur" wrote: On 02/06/2017 12:49 PM, Miles Gould wrote: > On 01/02/17 21:38, Lucas Alvares Gomes wrote: >> But, let me ask something, what the foundation really wants to achieve >> with this ? Cause I think we are conflating two things here:

Re: [openstack-dev] [ironic] End-of-Ocata core team updates

+1 to both, thanks for your contributions Vasyl and Mario!!! Sam On 17/02/2017, 09:40, "Dmitry Tantsur" wrote: Hi all! I'd like to propose a few changes based on the recent contributor activity. I have two candidates that look very good and pass the formal barrier of 3

Re: [openstack-dev] [ironic][bifrost][sushy][ironic-inspector][ironic-ui][virtualbmc] sub-project/repository core reviewer changes

+1 Sam On 23/08/2018, 21:38, "Mark Goddard" mailto:m...@stackhpc.com>> wrote: +1 On Thu, 23 Aug 2018, 20:43 Jim Rollenhagen, mailto:j...@jimrollenhagen.com>> wrote: ++ // jim On Thu, Aug 23, 2018 at 2:24 PM, Julia Kreger mailto:juliaashleykre...@gmail.com>> wrote: Greetings everyone! In

[openstack-dev] [ironic] Stepping down as core

ding I hope to see you there. The Ironic project has been (and I hope continues to be) an awesome place to contribute too, thank you Sam Betts sambetts __ OpenStack Development Mailing List (not for usage questions) Unsubsc

[openstack-dev] [networking-cisco] Poll to decide networking-cisco weekly meeting times

For those interested in participating, we are setting up a weekly meeting to discuss the development and design of networking-cisco. This meeting will be held on the #openstack-networking-cisco channel. If you are interested please use the link below to provide which of the dates and times you a

Re: [openstack-dev] [networking-cisco] Poll to decide networking-cisco weekly meeting times

ues rather than a project-specific channel. Regards -steve From: "Sam Betts (sambetts)" mailto:sambe...@cisco.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, September 20

Re: [openstack-dev] [ironic] ironic-inspector-core team update

+1 from me! Thanks for the contributions Milan :D Sam On 26/09/2016 10:24, "Dmitry Tantsur" wrote: >Hi folks! > >As you probably know, Imre has decided to leave us for other challenges, >so our >small core team has become even smaller. I'm removing him on his request. > >I suggest adding Milan

[openstack-dev] [networking-cisco] networking-cisco IRC meetings

TL;DR networking-cisco IRC meetings will be held bi-weekly on #openstack-meeting-3 starting from 2016/10/11 With the results of the doodle poll, and some pointers from Steve and Jeremy (thanks guys for the info) I've successfully organised the time and place for the networking-cisco IRC meeting

[openstack-dev] [networking-cisco] Meeting Reminder, 11th Oct 2016

Just a quick reminder that the first networking-cisco IRC meeting will be happening on #openstack-meeting-3 at 16:00 UTC. See you there, Sam __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: opens

[openstack-dev] [new][networking-cisco]

The networking-cisco development team are grateful to announce the release of: networking-cisco 4.0.0 This release is compatible with OpenStack Mitaka and Newton Download the package from: https://pypi.python.org/pypi/networking-cisco