-
-
-
-
Importing and synchronizing StyleBooks from GitHub repository
-
Simplified migration of Citrix ADC application configuration using StyleBooks
-
-
Use ADM log messages for managing and monitoring your infrastructure
-
-
Citrix ADC automation using Citrix ADM in Cisco ACI hybrid mode
-
Citrix ADC device package in Cisco ACI's cloud orchestrator mode
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Configure LBaaS V2 using command line
LBaaS V2 supports SSL offload with certificates managed by Barbican, certificate bundles (includes intermediary Certification Authorities), SNI support along with the regular load balancing features. LBaaS V2 supports only command line interface to run configuration tasks. LBaaS V2 API implementations are performed through Neutron LBaaS commands.
Note
Upload certificate and key to Barbican service when you require SSL offloading feature. Perform steps 1, 2, and 3 if SSL offloading is supported, else continue from step 4 to create a load balancer, a listener, a pool and a member.
-
Upload certificate to Barbican service using the following command:
barbican secret store --payload-content-type <content_type> --name <certificate_name> --payload<certificate_location> <!--NeedCopy-->
Example:
barbican secret store --payload-content-type='text/plain' --name='hp_server_certificate' --payload=" hp_server/tmp/server_certificate" <!--NeedCopy-->
-
Upload key to Barbican service using the following command:
barbican secret store --payload-content-type <content_type> --name <key_name> --payload<key_location> <!--NeedCopy-->
Example:
barbican secret store -- payload-content-type='text/plain' --name='shp_server_key' --payload="hp-server/tmp/server_key" <!--NeedCopy-->
Note
When you run these two Barbican commands to load the certificate and the key, the Secret href fields provide a location or url. This is where the certificate and the key are stored on the system where OpenStack is installed. Copy these links and provide these links as parameters when you create the container on Barbican service in step 3.
-
Create a container in Barbican service to store the certificate and the key using the following command:
In the command, replace
with the url that you obtained from the Secret href field when you uploaded the certificate. Similarly, replace with the url that you obtained from the Secret href field when you uploaded the key. barbican secret container create --name<container_name> --type<container_type> --secret<certificate_url> --secret<key_url> <!--NeedCopy-->
Example:
barbican secret container create --name='hp_container' --type='certificate' --secret="`certificate=http://localhost:9311/v1/secrets/e36a4a82-87e4-4873-9efe-55108875ef58 --secret="private_key=http://localhost:9311/v1/secrets/1b9e1a93-2aeb-4101-8002-e52acab987b0`" <!--NeedCopy-->
Copy the container href value. You have to provide the link to the container when creating the listener in step 6.
-
Set the environment variables in OpenStack. The variables enable the OpenStack client commands to communicate with the OpenStack services.
Example:
export OS_PASSWORD-hp
export OS_AUTH_URL=
http://10.106.43.15:35357/v2.0/
export OS_USERNAME=hp_user
export OS_TENANT_NAME=hp
export OS_IDENTITY_API_VERSION=2.0
export BARBICAN_ENDPOINT=”
http://10.106.43.15:9311/
”Note
Set these variables for every SSH session before running other commands. For more information about OpenStack environment variables, see OpenStack environment variables.
-
Create a load balancer using the following command:
neutron lbaas-loadbalancer-create --name <loadbalancer-name> <subnet-name> --provider <netscaler> <!--NeedCopy-->
Example:
neutron lbaas-loadbalancer-create --name hp-lb-test hp-sub1 --provider netscaler <!--NeedCopy-->
The status changes from PENDING_CREATE to ACTIVE after the load balancer is successfully created.
-
Create a listener using the following command:
neutron lbaas-listener-create --loadbalancer <loadbalancer-name> --name <listener-name> --protocol <protocol_type> --protocol-port <port_number> --default-tls-container-id<container_url> <!--NeedCopy-->
Example:
neutron lbaas-listener-create --name hp-lb-test-list --loadbalancer hp-lb-test --protocol TERMINATED_HTTPS --protocol-port 443 --default-tls-container-id `http://10.106.43.15:9311/v1/containers/d688676f-c256-4a0d-b84d-a310419dc0aa` <!--NeedCopy-->
Note
If you are creating a listener without SSL offload support, run the following command without providing locations to the container:
neutron lbaas-listener-create --loadbalancer <loadbalancer-name> --name <listener-name> --protocol <protocol_type> --protocol-port <port_number>
-
Create a pool using the following command:
neutron lbaas-pool-create --lb-algorithm <algorithm_type> --listener <listener-name> --protocol <protocol_type> --name <pool-name> <!--NeedCopy-->
Example:
neutron lbaas-pool-create --lb-algorithm LEAST_CONNECTIONS --listener demolistener --protocol http --name demopool <!--NeedCopy-->
-
Create a member using the following command:
neutron lbaas-member-create --subnet <subnet-name> --address <ip-address of the web server> --protocol-port <port_number> <pool-name> <!--NeedCopy-->
Example:
neutron lbaas-member-create --subnet hp-sub1 --address 15.0.0.15 --protocol-port 80 hp-lb-test-pool <!--NeedCopy-->
Monitoring OpenStack Applications in Citrix ADM
Your tenants can log on to Citrix Application Delivery Management (ADM) using their OpenStack credentials to monitor VIPs and pools created from OpenStack from any browser. The URL must be in the following format:
http://<mas_ip>/<admin_ui>/mas/ent/html/cc_tenant_main.html
Where, mas-ip-address
, is the Citrix ADM IP address that is registered with the OpenStack.
Note
OpenStack VIPs correspond to virtual servers in Citrix ADM.
OpenStack Pools correspond to service groups in Citrix ADM.
OpenStack Pool members correspond to service group members in Citrix ADM.
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.