Ask Your Question

AndyB's profile - activity

2019-02-21 07:45:29 -0500 received badge  Popular Question (source)
2018-08-01 18:06:12 -0500 asked a question Neutron Layer2 emulated network (flat?)

So I have an VM / appliance that is very broadcast / multicast heavy and I need to provide an emulated Layer2 network. If I create a standard OS::Neutron:Net network, it appears to be created as network_type "vxlan". From what I can tell, this is causing me problems in the application.

net_1:
type: OS::Neutron::Net
properties:
  name: { get_param: net_name_1 }
  admin_state_up: True

Everything I read seems to indicate I want to create a flat network. That seems to require me to use OS::Neutron::ProviderNet, but that also seems to require me to tie it to a physical port on the compute node... Is there a way around this?

Previously we've used this in an OpenStack environment with Contrail and Contrail just has a nice "Layer2 Network" button on the GUI... :/

Thanks!

2018-08-01 11:25:54 -0500 commented question virtio-scsi - Invalid image metadata

Absolutely correct. The team member who placed the image set the properties incorrectly, merging two together and creating one invalid one. Thanks!

2018-07-31 16:56:01 -0500 asked a question virtio-scsi - Invalid image metadata

Hello everyone. I've got a brand-new build OpenStack Ocata build based on the manual installation guide. I'm trying to load an image that has metadata tied to it that specifies "hd_scsi_model" to be ""virtio-scsi" and "hd_disk_bus" as "scsi". When I try to load this image via HEAT, I get the following error when the heat stack-create fails:

stack_status_reason:
    Resource CREATE failed: BadRequest:
    resources.cf_server_1: Invalid image metadata. Error:  
    Field value scsi,hw_scsi_model=virtio-scsi is invalid
    (HTTP 400) (Request-ID: req-9df3f708-5cc8-489c-82c8-734e2d15199e)

I'm guessing I need to add this sort of support, but have no idea what I'm really doing here... Help?!

Thanks a bunch!

2016-05-14 02:03:15 -0500 received badge  Famous Question (source)
2016-05-14 02:03:15 -0500 received badge  Popular Question (source)
2016-05-14 02:03:15 -0500 received badge  Notable Question (source)
2016-02-29 09:34:09 -0500 commented answer Mirantis Fuel - First time installing. cobbler failed to start

Nope. This is just a vanilla 7.0 install right from the Mirantis website.

It's quite possible there's something I'm doing wrong or have set wrong, but not knowing much about cobbler (or the rest of this for that matter), troubleshooting why cobbler isn't starting is beyond me at the moment...

2016-02-29 09:33:42 -0500 answered a question Mirantis Fuel - First time installing. cobbler failed to start

Nope. This is just a vanilla 7.0 install right from the Mirantis website.

It's quite possible there's something I'm doing wrong or have set wrong, but not knowing much about cobbler (or the rest of this for that matter), troubleshooting why cobbler isn't starting is beyond me at the moment...

2016-02-26 17:13:26 -0500 asked a question Mirantis Fuel - First time installing. cobbler failed to start

So this is my first time attempting to install Fuel (and first time playing with OpenStack for that matter.)

I'm running into issues during the installation of the fuel server. As directed by the installer, I can scan through the /var/log/puppet/bootstrap_admin_node.log file and it appears to be an issue with the cobbler installation.

Notice: /Stage[main]/Docker/Exec[build docker containers]/returns: ERROR: cobbler failed to start. ERROR: cobbler failed to start.

This is an installation on an HP blade server, so I've tried two different blades with the same failure in the same location...

Anyone have any insight? As I've said, I'm completely new to this. I'd really like to have my installation use Fuel, but I may just have to press on without it...

Thanks, AndyB