Last active
August 29, 2015 14:01
-
-
Save kmissoumi/7510e1b82a7c031373cc to your computer and use it in GitHub Desktop.
Setting Up OpenStack Network
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Still need to test and verify, had to work through some of the port versus network-interface deals, but looks clean. | |
| Big note is that the dash board did not show the updates, | |
| I'd expect there is something that runs every <variable_amount_of_time> that updates what was executed via neutron and shows it in the dash. | |
| IIRC the same thing is true for work completed in neutron, in that it does not show via nova...probably worth a ticket | |
| The "public" network is assumed created by SL for us, you can do a net-list to see if it's there or if someone made it with a different name. | |
| The 2nd network created by SL, the one that allows us to access MIND and WebRTC is usually named "extranetWAN". It is not created by default at this point. | |
| network name = <application>_network_<chef_environment>_<data_center> | |
| router name = <application>_router_<chef_environment>_<data_center> | |
| #variables removed | |
| neutron | |
| net-create <network_name> | |
| subnet-create --ip-version 4 --gateway <gateway_ip_address> --allocation-pool start=<pool_start_ip_address>,end=<pool_end_ip_address> <network_name> <network_CDIR> | |
| router-create <router_name> | |
| router-gateway-set <router_name> public | |
| router-interface-add <router_id> <subnet_id> | |
| #actual commands for blackflag4g-npe02 in EWR2 | L3, or is it J3? | |
| #network from https://github.com/att-innovate/blackflag-chef/wiki/Networks | |
| neutron | |
| net-create apigee-network-npe2-ewr2 | |
| subnet-create --ip-version 4 --gateway 10.13.3.1 --allocation-pool start=10.13.3.175,end=10.13.3.225 apigee-network-npe2-ewr2 10.13.3.0/24 | |
| router-create apigee-router-npe2-ewr2 | |
| router-gateway-set apigee-router-npe2-ewr2 public | |
| router-interface-add 722a0173-73d7-483e-8192-b8994ba0f164 ddb577bc-ce18-4e35-8f9e-54ce22cbb548 |
Unrelated, but might be nice to see if we have access to restart the DNSMASQ. Might be something in neutron.
Was not the case, was creating the network and router in the wrong tenant and wrong datacenter. Bravo!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Think changing the network name to
<app>_net_<chef_env>_<dc>would be better, just to keep it shorter.Also, probably should develop the procedure upfront to teardown the whole network. Of course, just the network's we create, we'd want to leave all the "public" and "extranetWAN" elements untouched. Not that I know we have the authority to delete them.