121
edits
Networking: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 10: | Line 10: | ||
You can create a network from the Create network button from both the <code> Network Topology</code> tab. Pick the name of the network with <code>Enable Admin State </code> and <code>Create Subnet box checked</code>, click next, pick a name for the subnet, in <code>Network Address Source</code> select <code>Allocate Network Address from a pool </code>, select the 172.16.0.0/12 pool and use the needed <code> Network Mask </code>, 24 will give you 256 addresses, click Next, make sure Enable DHCP is checked and click Create. You now have a new network. You can attach an existing VMs to that new network in the <code>Instance</code> tab by selecting <code> Attach Interface</code> in the <code>Actions</code> drop down menu of the instance. | You can create a network from the Create network button from both the <code> Network Topology</code> tab. Pick the name of the network with <code>Enable Admin State </code> and <code>Create Subnet box checked</code>, click next, pick a name for the subnet, in <code>Network Address Source</code> select <code>Allocate Network Address from a pool </code>, select the 172.16.0.0/12 pool and use the needed <code> Network Mask </code>, 24 will give you 256 addresses, click Next, make sure Enable DHCP is checked and click Create. You now have a new network. You can attach an existing VMs to that new network in the <code>Instance</code> tab by selecting <code> Attach Interface</code> in the <code>Actions</code> drop down menu of the instance. | ||
Not that VMs that will be solely attached to that network will have no internet access. You need to attach the router that has access to the Public-Network to the network to give it | Not that VMs that will be solely attached to that network will have no internet access. You need to attach the router that has access to the Public-Network to the network to give it access to the internet. | ||
=== Share the network with another tenant === | === Share the network with another tenant === | ||
This step can only be made with the [[OpenStack Client]], start by following the client's [[OpenStack_Client#Install_the_openstack_client|installation and configuration procedure]]. You also need the project ID of the tenant that will get | This step can only be made with the [[OpenStack Client]], start by following the client's [[OpenStack_Client#Install_the_openstack_client|installation and configuration procedure]]. You also need the project ID of the tenant that will get access right to your network. The project ID can be found in the [https://juno.calculquebec.ca/identity/ identity tab] of the Juno platform web site by clicking on the Projects menu. In this example, all code is run for the <code>po-test</code> projet, we will share the <code> share-net</code> network with the ''target project'' <code> c3g-dev</code>, <code> id = b84ceb857d8f40feb7eed5e972ec0e56</code>. | ||
Let’s start by looking at the networks of the <code>po-test</code> project: | |||
<syntaxhighlight lang="bash" line> | <syntaxhighlight lang="bash" line> | ||
| Line 31: | Line 31: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
We see the three default networks and <code>share-net</code>, the network that we | We see the three default networks and <code>share-net</code>, the network that we created in the previous step. We will share it by creating a [https://docs.openstack.org/neutron/latest/admin/config-rbac.html Role-Based Access Control (RBAC)] that targets the project <code>b84ceb857d8f40feb7eed5e972ec0e56</code> | ||
| Line 71: | Line 71: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
Here is how to | Here is how to list your Network RBACs and how to delete them. | ||
<syntaxhighlight lang="bash" line> | <syntaxhighlight lang="bash" line> | ||