...
Amazon AWS is currently hosting our RI for ONAP Continuous Deployment on my private account for now - I have requested a grant specific to the jenkins, kibana and cd instances.ONAP on Amazon EC2
see Cloud Native Deployment#AmazonAWS
see
Jira | ||||||
---|---|---|---|---|---|---|
|
ONAP Live AWS CD Servers
Server | URL | Notes |
---|---|---|
Live Amsterdam Cassablanca/master server | http://amsterdammaster.onap.info:8880 | Login to Rancher/Kubernetes only in the last 45 min of the hour Use the system only in the last 10 min of the hour Currently off until the account resets to the next bill on 2nd Jan |
Jenkins server | http://jenkins.onap.info/job/oom-cd/ | view deployment status, deployment (pod up status) Paused until 2 Jan 2018 |
Kibana server | http://kibana.onap.info:5601 | query "message" logs or view the dashboard |
CD Architecture
Abandoning GLIFFY for now - Confluence unstable - will past LucidChart capture shortly
name Gliffy Diagram
CD Demo Videos
20171210 showing a full CD job on the jenkins server |
| ||||||
...
DI 5: 20171112: Strategy for Manual Config of Rancher 1.6 for Auto Create/Delete of CD VM
ONAP on Kubernetes on Amazon EC2EC2#AWSCLIEC2CreationandDeployment
Code Block |
---|
#20171029 POC working on EC2 Spot using AMI preconfigured with Rancher 1.6 server/client aws ec2 request-spot-instances --spot-price "0.25" --instance-count 1 --type "one-time" --launch-specification file://aws_ec2_spot_cli.json aws ec2 associate-address --instance-id i-048637ed92da66bf6 --allocation-id eipalloc-375c1d02 # DNS record set type A changes take 20 sec to propagate the internet - for a dig command to see them aws ec2 reboot-instances --instance-ids i-048637ed92da66bf6 root@ip-172-31-68-153:~# kubectl cluster-info Kubernetes master is running at https://url.onap.info:8880/r/projects/1a7/kubernetes:6 |
...
Cannot get creation access to https://jenkins.onap.org/sandbox/ via Jenkins -> Configuring Jenkins
...
current ssh config
/var/jenkins_home/workspace/shared_aws_201801.pem
/var/jenkins_home/workspace/shared_aws_201801.pem obr..._aws_20141115.pem
Automated ONAP CD Infrastructure
We need sufficient resources to run two (amsterdam and beijing/master) deployments either hourly or on commit-trigger demand.
We also need devops infrastructure to provision the servers (an ARM DMZ jumbox), run the jenkins container and ELK containers (a single Kubernetes cluster)
Resources
ONAP Deployment Specification for Finance and Operations#AmazonAWS
name | provider | server | IP/DNS | port | resource group | type | vpc/vn | sg | acl | cert/pass | subnet | hosting | template | purpose |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ons-dmz | Azure | ons-dmz | ons-dmz.onap.cloud | ons-dmz | vm | bastion | Microsoft | dmz-jenkins | bastion/jumpbox | |||||
jenkins | Azure | ons-dmz-jenkins | jenkins.onap.cloud | 80 | ons-dmz-jenkins | dc | Microsoft | dmz-jenkins | jenkins | |||||
kibana | Azure | ons-dmz-kibana | kibana.onap.cloud | 5601 | dc | Microsoft | dmz-jenkins | kibana | ||||||
amsterdam-hourly | Azure | onap-amsterdam | amsterdam.onap.cloud | k8s | k8s | Microsoft | s | |||||||
beijing-hourly | Azure | onap-beijing | beijing.onap.cloud | k8s | k8s | Microsoft | ||||||||
chaos monkey b* | Azure | chaos.onap.cloud | k8s | Microsoft | hammer the system up/down | |||||||||
AWS | ons-dmz | bastion | bastion/jumpbox | |||||||||||
jenkins | AWS | ons-dmz-jenkins | jenkins.onap.info | 80 | ons-dmz | dc | admin m*n* | private | ||||||
kibana | AWS | ons-dmz-kibana | kibana.onap.info | 5601 | ons-dmz | dc | private | |||||||
amsterdam | amsterdam.onap.info | k8s | k8s | Amazon | ||||||||||
beijing | ons-brookhaven | beijing.onap.info | k8s | k8s | Amazon |
Performance
Static Server 4 hour Deploy Frequency
Resource Deployment Scripts
Azure
Code Block |
---|
# for recreation
ubuntu@ons-dmz:~$ sudo ./oom_deployment.sh -b amsterdam -s amsterdam.onap.cloud -e onap -r a_ONAP_CD_amsterdam_nodelete -t _arm_deploy_onap_cd.json -p _arm_deploy_onap_cd_a_parameters.json |
Links
...