vSphere Integrated Containers 1.4 – Upgrade 1/3



On May 15th VMware has released a new version of its own docker implementation product, vSphere Integrated Containers 1.4, as always it comes with enhancements that include but not limited to support for vSphere 6.7 and ROBO deployments, affinity rules (more on that in a future post) and some management portal improvements.

But today I wanna cover the upgrade process, I will break it into 3 phases for easier consumption;

- Upgrade vSphere Integrated Containers Appliance (This post)
- Upgrade vSphere Client Plug-in
- Upgrade Virtual Container Hosts (VCH)

To be honest the upgrade itself is not really an in-place upgrade, in fact, the process involves deploying a new VIC appliance and copying the relevant information from the previous appliance to the new one, including management portal, registry configuration and data.

The good thing about it is that it leaves you with an easy rollback option, since the previous appliance is kept intact, in case of any problem, you can just get rid of the new appliance and power the previous one back on and everything will still there just the way it was before the upgrade.

My actual environment compresses of a VIC 1.3 and one VCH connected to it;
obs: you can upgrade from any version later than 1.2.x
 
I also have a project (cnameetupsp), with a few images, which has been scanned for vulnerabilities and signed by Content Trust (another post I own you guys).


Let's start downloading and deploying VIC 1.4 since it's a new appliance, give it it's own IP address and hostname.
OVA deploy process is pretty standard among VMware's solutions, so I'm not going through it, but if you still have doubts the product's documentation is your friend.

Important: Make sure to use the Flex-based vSphere Web Client to deploy it, even if you are using vSphere 6.7, because HTML5 Web Client is not ready for VIC yet, although the deployment my succeed the configuration required for VIC to work might not be implemented properly.
 
Once the appliance is deployed access it through SSH. Make sure to enable it during OVA deployment.

Important 2: do NOT go to the Getting Started page of the new appliance, because it will initiate the services for a new set up and would cause the upgrade to fail, if you have done it, just deploy a new appliance ; )

Once on the new appliance console just run the upgrade script;
Run: ./etc/vmware/upgrade/upgrade.sh

The script will prompt you with the information about the vCenter where the previous appliance is provisioned, if you have an external PSC provide their information as well otherwise just leave it blank

Now you need to provide the information about your previous VIC appliance, make sure the appliance is power on and with SSH enabled, if not, power off the appliance and enable it through Permit Root Login within vApp Options.

There you go, just sit back, relax and watch the upgrade process running;
During the process, the relevant files are copied over and the old appliance is shut down.
If you need more information or for troubleshooting needs, the log is saved on /var/log/vmware/upgrade.log

Once it's done, just power on the new appliance and log in.
As we can see the upgrade was successful, my VCH is connected to the new VIC Appliance

My projects and images are there as well.


The only downside is that my images came unsigned, it's due as a new appliance comes with a different certificate from my previous one.
So, if you are using Content Trust you will have to plan it accordingly and resigned your images after the upgrade so the users will be able to pull and run them again.

That's all for today, stay tuned for the remaining upgrade phases; vSphere Plugin and Virtual Container Hosts.



via Latest imported feed items on VMware Blogs https://ift.tt/2GQ0dPR
RSS Feed

If New feed item from https://blogs.vmware.com/feed, then send me an email at kr

IFTTT

Comments

Post a Comment

Popular posts from this blog

Evernote cuts staff as user growth stalls

Image
Note-taking app Evernote has fallen on hard times of late, culminating in its latest spate of job cuts impacting 15 percent of its workforce (54 employees). CEO Chris O' Neil -- an ex-Googler who took the reins in 2015 -- announced the firings at an all-hands meeting earlier today, reports TechCrunch . In a message on the Evernote blog , O' Neill admitted he'd set "incredibly aggressive goals" for the company in 2018. He continued: "Going forward, we are streamlining certain functions, like sales, so we can continue to speed up and scale others, like product development and engineering." The layoffs follow an exec exodus just weeks ago and the company's recent brand refresh (complete with a refined logo and wordmark). But critics are more concerned about its product, especially the free tier, which they claim lacks the perks to...
Read more

The best air conditioner

Image
By Liam McCabe This post was done in partnership with Wirecutter . When readers choose to buy Wirecutter's independently chosen editorial picks, it may earn affiliate commissions that support its work. Read the full article here . After six summers of researching, testing, and recommending window air conditioners, we've learned that quiet and affordable ACs make most people the happiest—and we think the LG LW8016ER will fit the bill in most rooms. This 8,000 Btu unit cools as efficiently and effectively as any model with an equal Btu rating, and runs at a lower volume and deeper pitch than others at this price. Little extra features like a fresh-air vent, two-axis fan blades, and a removable drain plug help set it apart, too. The LG LW8016ER is a top choice for an office or den, and some people will find it quiet enough for a bedroom, too. If our main pic...
Read more

We won't see a 'universal' vape oil cartridge anytime soon

Image
Pre-loaded cartridges of cannabis concentrate are currently among the most popular means of consumption, and for good reason. They're discreet to use and easy to handle, a far cry from the dark days of 2016 when we had to dribble hash oil or load wax into narrow-mouthed vape pens by hand. But, frustratingly, an ever increasing number of oil cartridge manufacturers employ one-off design standards so that their products won't work with those of their competitors, thereby locking customers into proprietary ecosystems. We've already seen this with nicotine vaporizers -- which has a seen a massive rise in "pod systems" in the last few years, each outfitted with a unique canister and battery built to be incompatible with those of their competition. Is it too late for the burgeoning cannabis industry to set a universal standard for their product designs? ...
Read more