rlpple's profile - activity

Do you have a floating IP or External network assigned to it? Did you setup your security rules to allow outbound ping?

What is your instance Security Rules?

First to recap: Existing Instances : Can be pinged from the network namespace on the controllers. New Instances in the same tenant/project on the same network: From the same location the ping fails.

I have seen this behavior before during an Update.
Things to look at:

• Are the instances using the same security group?
  • You can try
  • sudo -i
  • ifdown eth0 ; ifup eth0 ; ifdown br-ex ; ifup br-ex ; ifup vlan10

If that works it may be related to https://review.openstack.org/#/c/395854/

Have you released all Floating IP's from all projects?

interesting so V2 no role assignment no issue. V3 issue. Excellent.

So your command seems to be missing the image name. Also did you source the devstack-admin rc?

my command after I source my adminrc

openstack image create --disk-format qcow2 --container-format bare --file cirros-0.3.5-x86_64-disk cirros --public

RDO (https://www.rdoproject.org/install/) is good too. All depends on the underlying OS you wish to use.

I use RHOSP to deploy to baremetal. RDO is the equivlent (https://www.rdoproject.org/install/)

Tried your steps on my undercloud node for Newton and then modified my rc file to read this (I used my ip not yours :) ) and it worked fine.
I believe the error is caused by using the V3 API and not the V2.
Try the below.

# Clear any old environment that may conflict.
for key in $( set | awk '{FS="="}  /^OS_/ {print $1}' ); do unset $key ; done
NOVA_VERSION=1.1
export NOVA_VERSION
OS_PASSWORD=demo
export OS_PASSWORD
OS_AUTH_URL=http://172.25.250.20:5000/v2.0
export OS_AUTH_URL
OS_USERNAME=myuser
OS_TENANT_NAME=myproject
COMPUTE_API_VERSION=1.1
OS_BAREMETAL_API_VERSION=1.15
OS_NO_CACHE=True
OS_CLOUDNAME=undercloud
OS_IMAGE_API_VERSION=1
export OS_USERNAME
export OS_TENANT_NAME
export COMPUTE_API_VERSION
export OS_BAREMETAL_API_VERSION
export OS_NO_CACHE
export OS_CLOUDNAME
export OS_IMAGE_API_VERSION

Hi, A few questions:

1. When pinging the router are you doing it from within the network namespace?
   • example: sudo ip netns exec "netns name" ping -c 1 -w 5 "router ip"
   • From router NetNS what does "ip a" and "route -n" show, and do they correspond to what you are expecting?

2. Next one
   • Delete all Security Rules
   • Create two new rules
   • one for ingress icmp
   • one for egress icmp
3. Can you post your router configuration
   • neutron router-show "router"
   • neutron net-show "network"
   • neutron subnet-show "subnet" (both of them)

Looking at how to create networks for a single tenant that repeat the vlans.

create switch2 assocaite to NIC2 and assign vlans 200 -220 switch3 associate to nic3 and assign vlans 200 - 220 switch4 associate to nic4 and assign vlans 200 – 220

through about nic 9 or 10 (We populate with 3 – 4 port nic in the hypervisor)

Then we create Instances and associate them to the switch we need for them;. Basically each nic is cabled to a Test cluster and all Test clusters have the same vLANs on them.

You can give a user access to a project in the member management section of the project. The real question can a configuration "security rule" cross projects, and I believe the answer is no.

It would be easier to create a new rule for the Project A that mimics SG-B.

Before getting into it too deep:

Did you clear your security rules and create new ones for the tenant for what you want? I find that the default seem to block everything and clearing them and create specific Ingress and Egress rules works best.

Question can you provide your complete environment?

Check this document for more about the image http://docs.openstack.org/developer/ironic/deploy/install-guide.html (Ironic Install Guide)

Starting with the Kilo release, Bare Metal service supports local boot with partition images, meaning that after the deployment the node’s subsequent reboots won’t happen via PXE or Virtual Media. Instead, it will boot from a local boot loader installed on the disk

Reading the doc a whole disk image is a fully function image ready to laydown on the drive.

You need to insure all tools are installed. Upon new install and fresh review of the logs the qemu-img was not installed. Once installed, using the /cirros-0.3.0-x86_64-disk.img image. I was abled to

glance image-create --name cirros-img --disk-format=qcow2 --container-format=bare < ./cirros-0.3.0-x86_64-disk.img cinder create --image-id fea9c58f-fa20-40a4-945a-d15c0239e025 --display-name cirros-img 10 and finally in horizon boot the image.

Going to Reinstall from scratch my passwords are out of sync. and thus the errors.

I need find an upload site. I can't upload files yet.

I cleared all my log files and found the following. I need to solve this first.

Just reviewed the logs and fou 2013-09-23 02:11:06 CRITICAL [cinder] (OperationalError) (1045, "Access denied for user 'cinder'@'192.168.124.81' (using password: YES)") None None Traceback (most recent call last): File "/usr/bin/cinder-manage", line 794, in <module> main() File "/usr/bin/cinder-manage", line 791, in main fn(*fn_args) File "/usr/bin/cinder-manage", line 219, in sync return migration.db_sync(version) File "/usr/lib/python2.7/dist-packages/cinder/db/migration.py", line 33, in db_sync return IMPL.db_sync(version=version) File "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/migration.py", line 76, in db_sync current_version = db_version() File "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/migration.py", line 88, in db_version return versioning_api.db_version(get_engine(), repository) File "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/session.py", line 123, in get_engine _ENGINE.connect() File "/usr/l

Running Grizzly release 1 Following the instructions from: http://docs.openstack.org/grizzly/openstack-compute/admin/content/instance-creation.html :

Upload Cirros image "cirros-0.3.0-x86_64-disk.img" into Glance . run glance image-list get my image id. Run the "cinder create --image-id 10bcfed8-7d98-48a6-8fef-829f5ae5c295 --display_name=mycirros --display_description "test" 5"

When I try to do a boot from volume in Horizon, the image just hangs in booting. I know I am missing a basic stepped. Any ideas would be helpful.