[Openstack] customizing trove instances security group
Amrith Kumar
amrith at tesora.com
Thu Feb 12 13:09:03 UTC 2015
Ali,
Mark's answer below would address the networking part, I just wanted to highlight the other pieces here that are that if your trove image has a public key (typically ~/.ssh/authorized_keys) and you know the user name, and an SSH server is installed and running, getting to the instance on SSH is merely a matter of adjusting the networking to allow access on route 22. There's nothing special in trove in this regard; that which you would do with Nova will work with Trove.
Hope that helps,
-amrith
| -----Original Message-----
| From: Mark Kirkwood [mailto:mark.kirkwood at catalyst.net.nz]
| Sent: Wednesday, February 11, 2015 6:02 PM
| To: openstack at lists.openstack.org
| Subject: Re: [Openstack] customizing trove instances security group
|
| On 12/02/15 09:09, Ali Nazemian wrote:
| > Dear all,
| > Hi,
| > I was wondering how can I customize the security group of created
| > trove instance in order to add ssh rule for the purpose of accessing
| > to the created instance using ssh.
| >
|
| You can set this via the command line tools e.g:
|
| $ neutron security-group-list
| $ neutron security-group-rule-create --protocol tcp \
| --port-range-min 22 --port-range-max 22 --direction ingress <sec group
| id>
|
| Cheers
|
| Mark
|
| _______________________________________________
| Mailing list: http://lists.openstack.org/cgi-
| bin/mailman/listinfo/openstack
| Post to : openstack at lists.openstack.org
| Unsubscribe : http://lists.openstack.org/cgi-
| bin/mailman/listinfo/openstack
More information about the Openstack
mailing list