#crowbar

f = forcing_ents[i] should be f = forcing_ents[fi] instead

never done a pull request :/

it's breaking CB2.0 wizard at the network stage

I just (finally) got a 2.0 ISO built and deployed. :)

zehicle_at_dell - how do I start the docker node deploy process?

planetrobbie: yes, I just encountered that myself.

judd7, you need to create a new container

by hand?

judd7, then you would curl post to the crowbar API to create the node

yes

Haven't before because it will onyl show up on real hardware that has an interface map, and all my testing so far has been on vms.

I will have a pull request out shortly with that and a few other updates.

zehicle_at_dell: did you ever get a chance to look at my latest attribute-related pull reqs?

k

victor_lowther, no. on my list for today

Just adding proper docker repos to the vagrant-crowbar-2 work.

zehicle_at_dell: ok.

I think you will like the direction I am taking attribs.

good, iot

it'd like to having something todo that I like doing

the docker I have on my vagrant box is only 0.5.1

0.7 is the new hotness

and is much nicer.

planetrobbie: OK, pushed a fix for the network recipe bustedness.

and added a couple of missing interface maps.

Great thx Victor, by the way I used an interface map on a VM.

victor_lowther, can I review those out of order from your other pulls?

hah

zehicle_at_dell: hmmm?

What other pulls?

· Make role attributes work, and add some to play around with in CB 2.0 [2/8]

planetrobbie: Out of curiosity, why did you use an interface map on a VM?

zehicle_at_dell: those are the only ones I have outstanding right now.

kk

I'm doing that now

I just pushed the network barclamp fixes without doing a pull request.

*hand slap*

Didn't know we could do without an Interface Map. I spent lots of time on network.json while doing the OpenStack Roxy deployment.

*sympathy hug* for planetrobbie

aahh

any interfaces that are not covered by an interface map are enumerated in ascending PCI bus order.

when the conduits are calculated.

Yep but when you have 4 Nics that get complicated without Interface map in VMware Fusion to assign the correct network to the vNics

hm.

never throught about that.

KVM always does exactly what I tell it to. :)

ahahh I work for VMware so …. aah

:)

victor_lowther, you were right - I do like these changes

looking at the pull approach, we may want to pull the hints into this too

I'll think about that as I review

victor_lowther, the major part of the review is done. more reading to do

OK.

victor_lowther, I have some questions but nothing blocking

would be good to see some docs (I can parse email into markdown)

I can add docs. I am not finished with it yet.

*thanks* victor_lowther

Wanted_attribs needs a bit of use before finalizing on how it should be layed out in the yaml.

But the pattern is there, and the code is merge able and useful as is.

+1