yahoo-eng-team team mailing list archive

[Ken'ichi Ohmichi <oomichi@xxxxxxxxxxxxxxxxx>]

I'm not sure now what is right usage of this feature.
Hopefully, some typos on the documentation would be nice.

** Also affects: openstack-manuals
   Importance: Undecided
       Status: New

** Also affects: neutron
   Importance: Undecided
       Status: New

** No longer affects: neutron

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1373832

Title:
  The source group of security group does not work

Status in OpenStack Compute (Nova):
  Incomplete
Status in OpenStack Manuals:
  New

Bug description:
  I created a security group with the other security group as the source
  group, and booted a server with the security group:

  $ nova secgroup-create source-any "secgroup for any sources" 
  $ nova secgroup-add-rule source-any tcp 1 65535 0.0.0.0/0
  $
  $ nova secgroup-create accept-ssh "secgroup for ssh" 
  $ nova secgroup-add-group-rule accept-ssh source-any tcp 22 22
  $
  $ nova boot --flavor m1.nano --security-groups accept-ssh --image cirros-0.3.2-x86_64-uec vm01

  but I could not access the server with SSH.

  According to http://docs.openstack.org/developer/nova/nova.concepts.html#concept-security-groups , the source group is
  considered as CIDR of acceptable source addresses and we can reuse it for new security groups.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1373832/+subscriptions