Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

Hi Michael So what does ironic driver-list say? May it be pxe_ipmitool? It would also be useful if you provide the conductor logs. On Sun, Mar 4, 2018 at 11:06 AM, Michael Still wrote: > Heya, > > I've been playing with bifrost to help me manage some lab machines. I must >

[openstack-dev] [Ironic][Bifrost] Manually enrolling a node

Heya, I've been playing with bifrost to help me manage some lab machines. I must say the install process was well documented and smooth, so that was a pleasure. Thanks! That said, I am struggling to get a working node enrolment. I'm resisting using the JSON file / ansible playbook approach,

[openstack-dev] [ironic] Re-adding Jim Rollenhagen to ironic-core

As time goes on it is natural for corporate interests to ebb and flow. Sometimes this comes as a new side project which complements OpenStack. Sometimes it is a negative hit where several contributors are abruptly in search of new jobs. Sadly, I think there is some normalcy to that. What we do

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

> No valid host was found. Reason: No conductor service registered which > supports driver agent_ipmitool. (HTTP 400) > > I can't see anything helpful in the logs. What driver should I be using for > bifrost? agent_ipmitool seems to be enabled in ironic.conf. Weird, I'm wondering what the error

[openstack-dev] [ironic] Polling for new meeting time?

Greetings everyone! As our community composition has shifted to be more global, the question has arisen if we should consider shifting the meeting to be more friendly to some of our contributors in the APAC time zones. Alternatively this may involve changing our processes to better plan and

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

Hi Michael, If you're using the latest release of biifrost I suspect you're hitting https://bugs.launchpad.net/bifrost/+bug/1752975. I've submitted anfox for review. For a workaround, modify /etc/ironic/ironic.conf, and set enabled_hardware_types=ipmi. Cheers, Mark On 4 Mar 2018 5:50 p.m.,

Re: [openstack-dev] [heat] heat-dashboard is non-free, with broken unit test env

On 03/02/2018 07:28 PM, Kaz Shinohara wrote: > Hi Thomas(zigo), > > I found an issue which is included in > https://review.openstack.org/#/c/548924/ (you did cherry pick last > night) > In short, this issue makes it impossible to install heat-dashboard.. > > I landed fix for this.

[openstack-dev] [tripleo] upgrading to a containerized undercloud

The use case that I'm working on right now is the following: As an operator, I would like to upgrade my non-containerized undercloud running on Queens to a containerized undercloud running on Rocky. Also, I would like to maintain the exact same command to upgrade my undercloud, which is:

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

Try setting the ironic_log_dir variable to /var/log/ironic, or setting [default] log_dir to the same in ironic.conf. I'm surprised it's not logging to a file by default. Mark On 4 Mar 2018 8:33 p.m., "Michael Still" wrote: > Ok, so I applied your patch and redeployed. I now

Re: [openstack-dev] [nova] vendordata plugin for freeIPA host enrollment

I was thinking about this the other day... How do you de-register instances from freeipa when the instance is deleted? Is there a missing feature in vendordata there that you need? Michael On Fri, Nov 11, 2016 at 2:01 AM, Rob Crittenden wrote: > Wanted to let you know I'm

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

Replying to a single email because I am lazier than you. I would have included logs, except /var/log/ironic on the bifrost machine is empty. There are entries in syslog, but nothing that seems related (its all periodic task kind of stuff). However, Mark is right. I had an /etc/ironic/ironic.conf

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

Ok, so I applied your patch and redeployed. I now get a list of drivers in "ironic driver-list", and I can now enroll a node. Interestingly, the node sits in the "enroll" provisioning state for ages and doesn't appear to ever get a meaningful power state (ever being after a five minute wait).

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

The ILO hardware type was also not loading because the required management and power interfaces were not enabled. The patch should address that but please let us know if there are further issues. Mark On 4 Mar 2018 7:59 p.m., "Michael Still" wrote: Replying to a single email

Re: [openstack-dev] [ironic] Polling for new meeting time?

Thx Julia, Another option is instead of changing meeting time, you could establish a tick-tock meeting, for example odd weeks for US-Euro friendly times and even weeks for US-Asia friendly times. On Mar 4, 2018 7:01 PM, "Julia Kreger" wrote: > Greetings everyone! >

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

On the enroll state, you can move it to available via manageable by setting the provision state to manage, then provide. Try an ironic node-validate to diagnose the issue, and make sure the ipmi credentials given can be used to query the nodes power state using ipmitool. Mark On 4 Mar 2018 9:42

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

Ahhh yes. The default (null) value of ironic_log_dir doesn't do quite what the author thought it did. https://review.openstack.org/549650 is a patch to correct that. Michael On Mon, Mar 5, 2018 at 8:42 AM, Mark Goddard wrote: > Try setting the ironic_log_dir variable to

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

I think one might be a bug in the deploy guide then. It states: "In order for nodes to be available for deploying workloads on them, nodes must be in the available provision state. To do this, nodes created with API version 1.11 and above must be moved from the enroll state to the manageable

Re: [openstack-dev] [openstack-helm] Question about API endpoints

Hi Yoshihiko, If you have physical LB in your environment, you might want to make use of NodePort for distributing the access to multiple controller nodes. In that case, it is recommended to set Values.network.external_policy_local to true so that you could eliminate unnecessary hops. Ingress

[openstack-dev] Question about API endpoints

Hi all, I try to deploy multinode OpenStack by openstack-helm and want to access OpenStack API endpoints from out of k8s nodes. To avoid service failure by node down, I think I need one virtual IP for the endpoints.(like Pacemaker) Could you show me how to realize that if you have any

[openstack-dev] [openstack-helm] Question about API endpoints

Hi all, # Resend with openstack-helm tag I try to deploy multinode OpenStack by openstack-helm and want to access OpenStack API endpoints from out of k8s nodes. To avoid service failure by node down, I think I need one virtual IP for the endpoints.(like Pacemaker) Could you show me how to

[openstack-dev] [devstack] Jens Harbott added to core

Hello, Jens Harbott (frickler) has agreed to take on core responsibilities in devstack, so feel free to bug him about reviews :) We have also added the members of qa-release in directly to devstack-core, just for visibility (they already had permissions via qa-release -> devstack-release ->