Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

SAN Certificate in VIO and How to Create With OpenSSL (78050)

Last Updated: 5/30/2023Categories: How toTotal Views: 5501Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

There is a need to change at least the public endpoints to be an FQDN instead of an IP and then apply a certificate to them. The installer only accepts an IP address for the public endpoint. The CSR generation tool does not allow for changing the common name. It only creates requests with the internal names (eg keystone.vio.cluster.local) and the IP Address.

Impact / Risks

Current certificate and private key should be backed up before proceeding.

kubectl -n openstack get secret certs -o=jsonpath='{.data.vio_certificate}'|base64 -d > ~/old_cert.crt
kubectl -n openstack get secret certs -o=jsonpath='{.data.private_key}'|base64 -d > ~/old_private.key

Resolution

Create a signing request on your OMS server.

Get an existing private key from deployment.

osctl get secret certs -o jsonpath='{.data.private_key}'|base64 -d > private.key

Create vio.cnf similar to:

[ req ]
default_bits           = 2048
default_keyfile        = privkey.pem
default_md             = sha256
prompt                 = no
distinguished_name     = req_distinguished_name
req_extensions         = v3_req
x509_extensions        = v3_req

[ req_distinguished_name ]
countryName            = US
stateOrProvinceName    = CA
localityName           = Palo Alto
organizationName       = VMware
organizationalUnitName = VIO
commonName             = 192.168.45.101

[ v3_req ]
basicConstraints      = CA:FALSE
subjectKeyIdentifier  = hash
subjectAltName        = @alt_names
keyUsage              = digitalSignature, keyAgreement, keyCertSign, keyEncipherment

[alt_names]
IP.1 = 192.168.45.101
IP.2 = 10.196.228.115
DNS.1 = keystone-api.openstack.svc.cluster.local
DNS.2 = pubapi.vioad.eng.vmware.com

Note: Update [ req_distinguished_name ] commonName and [alt_names] with your IPs and DNS.  [alt_names] is required. DNS.1 should remain keystone-api.openstack.svc.cluster.local

Create CSR to submit to the Public Authority or Internal CA.

openssl req -new -key private.key -out vio.csr -config vio.cnf

After receiving vio.crt signed by Public Authority append root CA cert to the end of vio.crt and place it in the new folder.

Import signed certificate to VIO with the command.

viocli import certificate -d crt/

Note:  If your import is successful the message will be:

2020/02/27 17:09:00 Begin to update certificates.
2020/02/27 17:09:00 Update certificates successful.

Restart vio services:

viocli stop services
viocli start services

Related Information

Add Certificates to Your Deployment

https://docs.vmware.com/en/VMware-Integrated-OpenStack/6.0/com.vmware.openstack.admin.doc/GUID-558CE36D-E515-4C23-99C5-C29D81CC2AC5.html

External DNS to FQDN/Ingress

https://docs.openstack.org/openstack-helm/latest/install/ext-dns-fqdn.html

Example of generating self-signed cert

openssl req -x509 -days 3650 -in vio.csr -key private.key -out vio.crt -config vio.cnf -extensions 'v3_req'

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
スナップショット LUN の再署名の操作が次のエラーで失敗する：VmfsAlreadyMounted (76989)

KB
•
vSAN 健全性サービス - ファイル サービス - ファイル サーバの健全性 (77165)

KB
•
执行抢占式故障恢复时，新的备用 T0 路由器的 BGP 对等互连停滞在主动状态 (77023)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Integrated OpenStack

Related Versions:

VMware Integrated Openstack 7.x

VMware Integrated OpenStack 6.x

Take Our Survey

Support Assistant