Loading...

Follow VMware vCloud Blog on Feedspot

Continue with Google
Continue with Facebook
or

Valid

Two months haven’t passed and we have a new version of HashiCorp Terraform vCloud Director Provider v2.2.0! You can now automatically download it via the terraform init command and find the corresponding documentation on the HashiCorp Terraform website:

https://www.terraform.io/docs/providers/vcd/index.html

In this particular release we had a primary goal of merging all of the open community contributions (a friendly reminder that Terraform vCD Provider is open-source). As such, this release packs the following main features.

Note that if you’d like to read about Terraform vCloud Director Provider in general, please see the previous article as well:

vCloud Director Embraces Terraform

v2.2.0 Features

First of all, there are two completely new resources for the provider level operations (i.e. system administrator):

  • New resource vcd_external_network – for automating creation of External Networks
  • New resource vcd_org_vdc – for automating creation of Organization VDCs

Then, the existing vcd_vapp_vm resource received a major improvement in the way it handles networks. As an outcome of that, it’s now possible to add multiple NICs to Virtual Machines. Also, you have access to the MAC addresses:

  • New argumentvcd_vapp_vm.network for multiple NIC support and more flexible configuration
  • New argumentvcd_vapp_vm.network.X.mac for storing the MAC address in Terraform state file

Another feature in vcd_vapp_vm and the related vcd_vapp resource is the ability to set metadata for vApp and its Virtual Machines separately:

  • New argumentvcd_vapp_vm.metadata for ability to add metadata to a VM
  • Improvedvcd_vapp.metadata argument to add metadata to the vApp directly

Moreover, a small topping to the cake of the same vcd_vapp_vm resource is a new flag for running hypervisors in a VM (hypervisor nesting):

  • New argument vcd_vapp_vm.expose_hardware_virtualizationfor ability to enable hardware assisted CPU virtualization

Last but not least, there’s also a handful of additions to the test suite to help avoid unwanted bugs. Of course, it’s committers who will feel this first. For instance, we’ve added test grouping by tags to support selective and parallel runs for the growing suite. In this context, if you like Go programming language and developing cloud automation tools, please consider joining our open-source community with a code contribution!

Please also see our changelog for details with links to related GitHub pull requests.

Now let’s look at examples on how you can use some of these new features.

Example of configuring an Org VDC

To begin with, let’s say we’re a provider and want to automate creation of Organization VDCs. It’s fairly easy to define an Organization VDC, but there are three points to be aware of.

  • First, use system administrator (as opposed to org administrator) credentials in the provider section of the Terraform template
  • Then, there are three allocation models supported in the allocation_model field, but one of their names differ from the one in the vCD GUI
    • AllocationPool – “Allocation pool”
    • ReservationPool – “Reservation pool”
    • AllocationVApp – “Pay as you go” (!) This name comes from vCD API and reflects that “AllocationVApp” model resources are committed to a vDC only when vApps are created
  • Last, there are two choices which argument to use in compute_capacityblock
    • limitis used with AllocationVAppmodel
    • allocatedis used with AllocationPool and ReservationPoolmodels

So, let’s take a look at an example for the VDC with the AllocationVApp (“Pay as you go”) model. Please note the in-line comments which reflect the above notes.

provider "vcd" {
  url      = "https://${var.vcd_host}/api"
  user     = "administrator" # Need system administrator privileges
  org      = "System" # Connecting to System because we're administrator
  password = "${var.admin_pass}"

  allow_unverified_ssl = "true"
}

# v2.2.0+
resource "vcd_org_vdc" "vdc-pay" {
  org = "myorg" # Tell in which Org to create the VDC

  name        = "TfPayVDC"
  description = "Terraform created VDC"

  allocation_model  = "AllocationVApp" # The "Pay as you go" in vCD GUI
  network_pool_name = "vc1-TestbedCluster-VXLAN-NP"
  provider_vdc_name = "vc1-TestbedCluster"

  network_quota = 10

  memory_guaranteed = 0.55 # Translates to percentage 55%
  cpu_guaranteed    = 0.50 # Translates to percentage 50% 

  compute_capacity {
    cpu {
      limit     = 3123 # For "ReservationPool" and "AllocationPool" models, use "allocated" instead of "limit"
    }

    memory {
      limit     = 4123 # For "ReservationPool" and "AllocationPool" models, use "allocated" instead of "limit"
    }
  }

  # Note how "storage_profile" can be defined multiple times
  storage_profile {
    name    = "*"
    limit   = 0
    enabled = true
    default = true
  }

  storage_profile {
    name    = "Development"
    limit   = 0
    enabled = true
    default = false
  }

  enable_thin_provisioning = true
  enable_fast_provisioning = true

  delete_force     = true
  delete_recursive = true
}

Please see Org VDC documentation page for more details:

https://www.terraform.io/docs/providers/vcd/r/org_vdc.html

Example of a VM with multiple networks

To continue, let’s take a look at an example snippet which defines a VM with three NICs and some advanced parameters.

  • Three NICs
    1. Connected to vApp network
    2. Connected to Org VDC network
    3. Not connected at all
  • Hardware assisted CPU virtualization enabled
  • Custom metadata set

It’s important to note that:

  • You define more than one NIC by creating more than one network block
  • Order of the network blocks gets reflected in the operating system

As in the previous example, please see the in-line comments for explanations as well.

provider "vcd" {
  url      = "https://${var.vcd_host}/api"
  org      = "myorg"
  vdc      = "myorgvdc"
  user     = "orgadmin" # In this case we *don't* need system administrator privileges
  password = "${var.org_pass}"
 
  allow_unverified_ssl = "true"
}

resource "vcd_vapp_vm" "vm11" {
  vapp_name     = "TfVApp"
  name          = "TerraformVM11"
  catalog_name  = "OperatingSystems"
  template_name = "Linux"
  memory        = 384
  cpus          = 1

  # v2.2.0+
  network { # We can define as many "network" blocks as needed
    type               = "vapp"
    name               = "TfVAppNet"
    ip_allocation_mode = "POOL"
    is_primary         = false
  }

  # v2.2.0+
  network {
    type               = "org"
    name               = "TfNet"
    ip                 = "192.168.0.11"
    ip_allocation_mode = "MANUAL"
    is_primary         = true
  }

  # v2.2.0+
  network {
    type               = "none" # This NIC won't be connected to a network
    ip_allocation_mode = "NONE"
  }

  # v2.2.0+
  expose_hardware_virtualization = true

  # v2.2.0+
  metadata {
    # The attribute names below are user-defined (they land to vCD together with values)
    role    = "test"
    env     = "staging"
    version = "v2.2.0"
  }

  accept_all_eulas = "true"
}

Please see VM resource documentation page for more details:

https://www.terraform.io/docs/providers/vcd/r/vapp_vm.html

Next Steps

Most importantly, please give it a try! And if you have questions, don’t hesitate to ask. You can do it by joining our Slack channel #vcd-terraform-dev through VMware {code} or filing an issue in the Terraform vCloud Director Provider repository.

Hope to hear from you!

The post Terraform vCloud Director Provider v2.2.0 Released appeared first on VMware Cloud Provider Blog.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 
Cloud Spot Podcast :2nd episode vCloud Availability Disaster Recovery

Please welcome Daniel Paluszek a Staff Solutions Engineer to talk about our newest release of vCloud Availability. Why is this release so special? Well, this is the converged solution architecture for our disaster recovery solution – exceeding all past architectures and capabilities into a very simple to deploy, simple to configure and use, disaster recovery (DR) solution for your vCloud Director tenants!

Daniel is a vCloud Availability expert who has done a lot of enablement for partners in vCloud Availability and he has a lot of exposure in provider DR solutions. You can view the playlist of Daniel’s vCloud Availability light boards on the YouTube channel http://bit.ly/vCAvPlaylist.

We discuss DR in the marketplace today, the fit for vCloud Availability in the market and how the customer is presented the DR offering. vCloud Availability provides cloud to cloud DR (vCloud Director virtual data center to virtual data center) and from a customer vCenter to a vCloud Director virtual data center, all in self service! Do you know the differences between cold and warm migration? Did you know vCloud Availability can be used or migration as well as protection? Learn about this use case and others on the podcast.

As usual, if you would like to provide feedback or suggestions for the podcast please email cloudspot@vmware.com

Resources mentioned: How do I get access to Cloudspot?

The podcast is available on Apple Podcasts, Google Podcasts, ZenCast & Spotify – search for “Cloudspot” or click over to our website: http://www.cloudspotpodcast.com.

The post Cloudspot podcast focus on vCloud Availability for Disaster Recovery appeared first on VMware Cloud Provider Blog.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

In a previous blog post, we walked through How to Signup for the Flex Pricing Model. Now let’s walk through how to submit monthly reports. The Flex Pricing Model is a new consumption model that replaces the old bundles that have been around for years. They give partners much more flexibility in how they consume VMware technology and help them create the services for their customers.

Let’s go over a couple tidbits before first:

vCloud Usage Meter Support – In the past, the Usage Meter appliance needed to be updated to report new bundle changes. This time around, that is not the case. Partner still need to run Usage Meter 3.6 and up, but do not need to update the appliance for Flex Model reporting.

Translation of Old Bundle data to Flex Model – Each month when you report your monthly usage, you will still input data using the old bundle names into your monthly report in the Business Portal.The Business Portal will then translate the bundle data to Flex Pricing Model for you. For partners in the VCPP before Flex was GA, they will be provided Price Protection for bundles with a price difference.

vCloud Usage Insight + Flex – Although Usage Insight is not necessary for Flex reporting, it does fill in the report for you so that you do not have to. This is still a huge advantage, especially for partners with more than one Usage Meter appliance in their environments.

End-User Reporting – Not available in Flex Pricing Model at this time.

With that out of the way, let’s walk through submitting a report in the business portal on the Flex Pricing Model. We will be inputing the data into the monthly report as if we are a partner that is not currently using vCloud Usage Insight. For partners that have adopted automatic reporting, go ahead and skip to step 2!

Step 1: Open and Fill out your Report

It’s the beginning of the month and it’s time to submit your monthly licensing consumption usage. You open up your monthly report as you always do. Let’s enter the bundle based data into the report like you have done every month. The old bundle names are still there, no worries.

Take note the total points in the top right of the screenshot, this report shows a total of 20,500 points before translation. I reported a little bit of every single bundle to help show how Core Bundle an Add-On usage is aggregated regardless the combination of old bundles used.

Step 2: Review the Translated Usage

Once you click next, you will be taken to the Rental Flex Usage page (Flex Translation). On this page, the business portal shows the usage based on how it would appear if you aggregated the Core bundle and Add-On products separately. On this page you can see that the total usage from the previous page matches the translation page. These fields will be greyed out as you cannot edit a calculated number.

Take note of how there are duplicates of the usage from the same products. There is a second SKU for the same add-on but with a lower Points Per Unit. This is the 3 Year Price Protection for partners that were already in VCPP. If you click on the information icon for the Flex Core Bundle, you can see how much vSphere usage came from each of the bundles that were reported. This shows the total aggregate of Core Bundle.

To see an add-on product’s aggregate usage after translation, like vRealize Operations Manager,  you can also click on the information icon and see which bundles contributed to that add-on’s usage.

Step 3: Submit the Report

Go ahead and click next on the translation page and you will be taken to the summary page. Here you will see information about total cost based on your contract. You are now ready to close out the report and submit the usage on to your aggregator. Congrats, you’ve completed your Flex Pricing Model report. That wasn’t too bad, was it?

If you have any feedback or additional questions, feel free to reach out to your Aggregator, VMware Representative or VCPP Operations. We will be presenting more vmLive webinars throughout 2019 to provide partners with enablement.

The post How to Report Monthly Usage with the Flex Pricing Model appeared first on VMware Cloud Provider Blog.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

We are thrilled to announce a major update to the VMware Cloud Provider Program (VCPP) that deliver partners the flexibility and control to granularly consume VMware solutions and easily build and offer new services.

The VMware Cloud Provider Program (VCPP) has grown over the years to help partners build cloud environments for their customers. Throughout this time, the program focused on giving partners a licensing model that provide different bundles of solutions that matched the needs of many partners. These bundles helped them grow their business based on what they needed when they needed it.

However, we recognize that not all partners have the same needs and what works for one may not work for another.

New Flexible Licensing

That brings us to now! VCPP Partners can now sign up to move to the next pricing model called Flex! Delivering the biggest change in years, we are adapting to our partner’s feedback and helping them consume the products they specifically need, when and where they need it. Want to know how? Check out this other blog article HERE.

The Flex Pricing Model brings a sense of “Choose your own adventure” to running a cloud business. Now partners can utilize one standard core set of products that all partners get access to, then build on top of that foundation. They can select any add-ons, in any order, for the products they want to deliver services to meet their customers needs.

Differentiate Yourself with Custom Services

This helps partners who run businesses in specific markets like DR-as-a-Service, Monitoring-as-a-Service or new platforms like PKS, build for their exact needs.  Now more than ever, partners can say yes to more deals as they use VMware products for their cloud enterprise. The point of the Flex Pricing Model is to take VMware’s consumption pricing, and add that same flexibility to creating your own bundles.

The future for VCPP Partners is bright, with options to expand into markets like:

  • DRaaS
  • Monitoring-aaS
  • K8S-aaS
  • and more!

Learn More and Make the Switch Today!

We are excited to bring this flexible model to our partners and hope to see more success as they meet their customers’ demands in the ever-growing cloud provider business. If you want to know more, head over to Partner Central and check out pricing in the new Product Usage Guide and Flex Pricing Model FAQ.

The post Choose Your Own Cloud Adventure with VCPP Flex Pricing appeared first on VMware Cloud Provider Blog.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Since mid-2018, the VCPP Team at VMware have been talking about the new Flex Pricing Model that is coming. This is the new consumption model that allows partners to build their bundles and create the services that they want or their customers need. At the beginning of May 2019, VMware released the pricing information to partners through an updated Product Usage Guide and a Flex FAQ. Starting today though, partners are able to sign up and transition!

So let’s dive in on how to do just that.

Step 1: Login to the Business Portal

Before we begin, it should be noted that you need to be a user with Service Provider Administrator role to complete the signup. This is to make sure that not just anyone can convert your contract.

Click on this link to go to the Business Portal and login: https://vmware.iasset.com

Once you login, you will see the banner text on your dashboard guiding you to signing up. If you don’t have permissions to perform the signup or complete the follow steps, ask your Contract Owner to add the role to your user under System Admin > Users > Edit User or have the Contract Owner complete the signup.

Step 2: Edit your Service Provider entity

Service Provider Administrator role users will have menu items available that other roles do not. Go ahead and click on System Admin in the menu bar like shown in the thumbnail below.

Once on the Service Provider page, click on the Edit button to the left of your Service Provider name. That should look like a paper and pencil icon. This will open a pop up with details about your organization.

Towards the bottom of that pop up window, you will see a check box to “Opt-in to Flex Pricing”. Let’s click on that.

Step 3: Complete the Signup

You should now see some terms & conditions. These are important and we want to make sure you read through all of it. I promise, it’s not that long, but it is important. One interesting option you will see is the ability to choose the month when you will first report Flex model. So if you agree to the terms and conditions now, choose your first month and click accept!

You will see one last confirmation. This is just because the signup is a one way process and cannot be reversed. If you are ready, click OK and now you are all set!

Thats all there is to it! In the next blog post we will walk you through what a monthly reporting process will look like.

Please Note: If you do customer monthly reporting, have custom bundles / pricing, or actively report the 5 Point Standard bundle, please reach out to your Aggregator or VMware representative before signing up.

The post How to Sign Up for the new VCPP Flex Pricing Model appeared first on VMware Cloud Provider Blog.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 
Introducing CloudSpot: Our New Podcast to Keep you Cloud Ready! What is CloudSpot?

CloudSpot is a new podcast that discusses the latest cloud technologies from the Cloud Providers’ perspective and covers new products and updates from the VMware Cloud Provider team. The podcast series is not a detailed technical product pitch (although we will cover products!), rather it addresses real service provider challenges and customer use cases.

New Content for Different Cloud Personas

We will discuss Cloud as a Persona – looking at cloud from the differing persona viewpoints from partners, customers and VMware staff. Viewpoints and topics covered will include:

  • Operations management; challenges and solutions for cloud automation, Configuration & Service Management
  • Financial management; challenges and solutions for cloud metering, balancing, billing, violations & credit management
  • Security management; challenges and solutions for cloud policies, rules, reporting and compliance
  • Capacity management; challenges and solutions for cloud usage vs demand and quality
  • Product management: challenges and solutions for cloud services; architecture, pricing, functions and capabilities
  • …and many more!
Why: Simple, Portable Communications

We all lead busy lives, and we’re thrilled you’re making time to read our blogs! We know that’s not always possible and that we have had varying success in communicating to and helping enable all of our cloud providers.

Especially for those on the run or in the car, the new podcast provides an easier way to consume the latest information on cloud technologies and VMware solutions for our cloud providers.

Episode 1: Inside Look into VMware’s Cloud Practice

Today we are launching our first podcast, featuring myself @Guy Bartram as your host and @Dan Gallivan– Sr. Director of the Global Cloud Practice within the VMware Cloud Provider Program. We will be talking about the Cloud Practice and Dan’s experience with Cloud Providers as well as covering some of the recent major program and product announcements.

You can expect between 1 – 2 podcasts per month, perhaps more if time permits!

How do I get access to Cloudspot?

Search iTunes or your favourite Podcast application for “Cloudspot” or click over to our website: http://www.cloudspotpodcast.com.

If you have feedback regarding the podcast or any ideas, please email cloudspot@vmware.com.

The post Introducing CloudSpot: Our New Podcast to Keep you Cloud Ready! appeared first on VMware Cloud Provider Blog.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

We are pleased to announce that CloudMasters Event (formerly Delta Force for Cloud Providers) has been launched for LATAM geo. This is our Premier Partner Enablement initiative, where our VCPP/MSP specialists will be sharing not only the foundations of the VMware Cloud Provider Platform (composed by VCPP and MSP) but also conducting deep dive enablement in several use cases being enabled by our technology for Cloud Providers on both sides: VCPP and MSP programs!

It will be delivered online across a series of four (4) separate online sessions where our VCPP/MSP specialists will conduct specialized training about our core strategies and market trends.

Webcast Schedule (Times under Eastern Time – US and Canada as reference)

  • May 29, 2019 1:30 PM – 5: 30 PM EST (VCPP 101)
  • May 30, 2019 1:30 PM- 5: 30 PM EST (VCPP Use Cases)
  • June 5, 2019 1:30 PM- 5: 30 PM EST (MSP 101)
  • June 6, 2019 1:30 PM- 5: 30 PM EST (MSP Deep Dive)

REGISTRATION LINK: Click here.

NOTE: Event will be held in Spanish for all LATAM-based Partners.

AGENDA LINK: Download the CloudMasters AGENDA

The post Announcing VMware CloudMasters 2019 – LATAM Edition appeared first on VMware Cloud Provider Blog.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 
Usage in VMware Cloud Provider Hub Series Part 2 – Deep dive into detailed hourly usage report

Understanding usage is key for providers to plan and study the consumption of cloud services of their end customers in VMware Cloud Provider Hub.

In the previous blog, I covered the different features of Usage for Provider and tenant that VMware Cloud Provider Hub offers. In this blog, I will explain the detailed usage report and interpreting the calculation behind aggregated usage and effective usage of a SKU for a service consumed using an example of host usage in VMware Cloud on AWS.

This blog requires prior knowledge of basics of VMware Cloud Provider Hub and part 1 of this blog series.

How to interpret usage displayed in VMware Cloud Provider hub

Usage is available for the usage period in arrears for the services consumed in VMware Cloud Provider Hub.

In order to understand the usage displayed in VMware Cloud Provider Hub, we need to understand some key definitions and basics of pricing for the service for which usage is explained – here VMware Cloud on AWS.

Some key definition What is a SID
    • It is an unique alphanumeric identifier assigned to a customer account for ordering purposes
On-demand SID
    • Is a SID, which is created when service is activated for the very first time and all on demand usage for that organization appears under this SID. It does not have an end date.
Term or reservation SID
    • Is a SID which is created for every term subscription in that organization for each service. Based on whether it is a 1-yr or 3-yr term subscription, the end date will vary
Overage
  • Overage charges is the charge that appears every month in the bill in Business Portal and this DOES NOT appear in VMware Cloud Provider Hub
VMware Cloud on AWS and host usage

VMware Cloud on AWS is a service on VMware Cloud Provider Hub, which is an integrated cloud offering jointly developed by AWS and VMware to deliver a highly scalable , secure and innovative service that allows organizations to seamlessly migrate and extend their on-premises VMware vSphere-based environments to the AWS Cloud running on next-generation Amazon Elastic Compute bare metal infrastructure.

VMware Cloud on AWS usage can be for compute, storage or network. The hosts usage can be of two types – On-Demand Instance and Reserved Instance .

On-Demand Instance

Hosts are spun up always on demand. On demand consumption for VMware Cloud on AWS starts when you hit DEPLOY SDDC in VMware Cloud on AWS service

In our example

One SDDC with 3 hosts is deployed in US West on 1st Feb 2019 at 4 PM Palo Alto time zone

The time can be also obtained from the Activity Log of the service

The number of hosts running for every hour appears under Usage Qty in the downloaded usage csv file in VMware Cloud Provider Hub.

Note: This csv file can be downloaded only for usage in arrears. Here it can be downloaded only after 5th March 2019

Reserved Instance

A reserved instance is not a physical instance.

  • It is a billing discount applied to the usage of the On-Demand instance .
  • It is only applicable against the On-demand instance in the same organization and same region
  • It is created in VMware Cloud on AWS service under Subscriptions.
  • It has a long term commitment of 1 or 3 years

Here a reserved subscription is created for 1 host in US West Oregon.

The number of reserved hosts against that sku appears as Commit Qty in the downloaded usage csv file from VMware Cloud Provider Hub.

Hourly overage host usage calculation

The hourly overage usage calculation for host is computed as below

  1. Number of hosts running in that organization per hour appears as Usage Qty
  2. Number of reserved instance in that organization in that region appears as Commit Qty
  3. Billable Qty = Usage Qty – Commit Qty

For the first hour the billable qty is 1.20667 host hour

For the second hour the billable qty is 1 host hour and so on…

Line Items in downloaded usage report for VMware Cloud on AWS service

The line items in downloaded usage report VMware Cloud on AWS service for the period of Feb 2019 has been explained with numbered list.

  1. tenant org id
  2. tag – A unique identifier for each organization particularly used in apis for filtering
  3. on-demand SID – here – M545711361
  4. sku for host in US West (Oregon) as the SDDC was deployed in US West – here – VMware Cloud on AWS – Core Service – US West (Oregon) – Per i3 Host-Hourly Usage
  5. Billable Usage Timestamp – Is logged every hour for the host from the time the hosts were deployed and till they are up and running.
    1. The time is in UTC . So since the SDDC was deployed on
      1. 1st Feb 2019 at 4:20 PM, the timestamp appears as 2019-02-02T00:00:00.000Z
  6. PriceIs the MSRP list price for that sku

Here the MSRP price $8.3681 for one host in US West and this field always displays the latest price. For any pricing details refer to latest pricing here.

  1. Usage Qty is the number of hosts deployed on demand – here 3 hosts on demand for the second hour = 3
  2. Commit Qty is the quantity to indicate the number of reserved instance – here reserved instance (a.k.a subscription) was created for 1 host in US West = 1
  3. Billable Qty per hour is the Usage Qty – Commit Qty – On-demand host usage per hour for that sku minus no of reserved instance (subscription) = 3 – 1 = 2 hours of host usage for that sku

Mapping the host usage between downloaded usage report and as it appears in VMware Cloud Provider Hub

If we sum all the Usage Qty for the host sku in the downloaded usage report for the sku COA-A1ASA-C we get the aggregate usage in VMware Cloud Provider Hub.

Similarly if we sum the Billable Qty for the host sku in the downloaded usage report for the sku COA-A1ASA-C we get the aggregate effective usage in VMware Cloud Provider Hub

Usage in Hub for the sku – The aggregate usage and aggregate effective usage appears in hub as below

As you can see, it is extremely simple to view and download the aggregated usage report or detailed hourly usage report for any organization , be it provider organization or tenant organization. Consolidated report for all organization can also be downloaded by the provider.

End customers can view their prior aggregated usage per sku for all services consumed for their organization.

In part 3 , I will provide examples using usage api.

Additional Resources

Learn more about VMware Cloud Provider Hub using links below

The post Usage in VMware Cloud Provider Hub Series – Part 2 appeared first on VMware Cloud Provider Blog.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 
Usage in VMware Cloud Provider Hub Series Part 1 – Highlighting features of usage

VMware Cloud Provider HubTM offers Managed Service Providers consolidated view of usage for all their customers, which helps them with customer lifecycle management. In this blog series, I discuss the different features of usage as offered in VMware Cloud Provider Hub as well as understanding the usage details. Providers can use this detailed customer-level usage and use their own billing system to attach appropriate rate cards and generate customer bill for cloud services consumed by them.

VMware Cloud Provider Hub is a single portal for cloud providers to manage and provide VMware Cloud services delivered to their customers.. VMware Cloud services consists of a broad set of services that allows the creation, management and monitoring of public, private and hybrid cloud resources.

Providers need to be a VMware Cloud Provider Partner and need to have an active commit contract through an aggregator before onboarding to VMware Cloud Provider Hub. This commit contract is created in the VMware Cloud Provider Program (VCPP) Business Portal.

If you are new to VMware Cloud Provider Hub or know how to onboard to VMware Cloud Provider Hub, refer to blogs published earlier here.

Usage in VMware Cloud Provider Hub is available under Billing & Subscriptions tab in both provider and tenant console when you login to console.cloud.vmware.com.

Provider and Customer-level Usage in VMware Cloud Provider Hub Viewing prior usage

The different options for viewing prior usage in VMware Cloud Provider Hub is explained with screenshots from Cloud Provider Hub and mapped to the numbered list below.

Providers in Provider organization can view usage
  1. for Provider Org (by selecting the provider org), and
  2. any of the tenant orgs (by selecting the required tenant org) for
  3. default usage period, which is last month. Basically if you are in the month of March 2019, the usage for the month of Feb from 1st Feb to 28th Feb (both dates inclusive) .

Usage details

  1. includes MSRP Price of the sku – The MSRP price is always the latest MSRP price of every sku. It is highly recommended to use this for the previous month only to generate bills for end customers.
  2. Includes usage aggregated per sku
  3. Includes effective usage aggregated per sku (explained later the definition of effective usage)
  1. are filterable on service, sku and price
  2. can be downloaded as detailed hourly usage report as a csv file for the selected view (selected org and selected period)
  3. can be Downloaded as detailed hourly usage report as csv file for all organizations for the selected period – provider as well as all tenant organizations
Providers in a tenant organization can view usage
  1. only for that tenant org
  2. for default usage period, which is last month. Basically if you are in the month of March 2019, the usage for the month of Feb from 1st Feb to 28th Feb (both dates inclusive) is displayed
  3. usage aggregated per sku
  1. filterable on service
  2. filterable on sku
  3. can download the detailed hourly usage report as a csv file for the selected view
Tenants in tenant organization can view usage
  1. only for that tenant org
  2. for default usage period, which is last month. Basically if you are in the month of March 2019, the usage for the month of Feb from 1st Feb to 28th Feb (both dates inclusive) is displayed
  1. usage aggregated per sku
  2. filterable on service
  3. filterable on sku
  4. can download the detailed hourly usage report as a csv file for the selected view
Roles with permissions to view Usage Provider Users with the following roles can view usage in provider org as well as tenant org
  • Provider Admin
  • Provider Operations Admin
  • Provider Accounts Admin – restricted to the tenants assigned
  • Provider Billing User
Tenant Users with the following roles can view usage in tenant org
  • Tenant Administrator
  • Tenant Billing User
Detailed hourly usage report

Cloud Provider Hub detailed usage report can be downloaded as a csv file. It contains granular hourly usage for every organization for all skus consumed for all services. A sample of the report Is shown below.

In this blog I have touched upon the different features of Usage that VMware Cloud Provider Hub offers for Provider and their end customers.

In Part 2: Deep dive into detailed hourly usage report – I will deep dive into understanding the detailed hourly report as well as how you arrive at the aggregated usage and aggregated effective usage of a SKU host usage in VMware Cloud on AWS as an example.

Additional Resources

Learn more about VMware Cloud Provider Hub using links below

The post Usage in VMware Cloud Provider Hub Series – Part 1 Highlighting features of usage appeared first on VMware Cloud Provider Blog.

Read Full Article
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

VMware vCloud Availability 3.0 (vCAv) allows for self-serviceability by the provider and tenants for disaster recovery services. When working with the customer to set up the service, it is important to understand the scope of responsibility for the service and how it will be managed. This blog will focus on different factors impacting replication in vCloud Availability.

If we start by looking at the general architecture of the platform, it is designed in a way that allows for replication management from vSphere or vCloud Director. vCloud Availability supports cloud-to-cloud replication as well as vSphere-to-cloud replication. This means that vSphere users can set up replications in the vCloud Director UI. This also means that vCD users may have visibility into vSphere to set up replications as well.  So what happens if we want to be able to segregate access between the vSphere users and the vCloud Director users and define domains of control. With vCloud Availability 3.0, this is possible.

Controlling vCloud Availability access from vCloud Director

For the enterprise administrators, when deploying the on-premises vCloud Availability appliance, there is an option under Cloud Details, Allow Access from Cloud, that can be set that controls the ability of users to set up new replications from vCD. If this is disabled, vCD users cannot remotely browse vCenter. The only way to establish new replications is leveraging through vCenter. If this option is enabled, new replications can be established from either side.

If a vCloud Director user tries to set up a replication when this is disabled, they will receive an appropriate permissions error.

vCloud Director users still have visibility into existing replications and can edit details and perform migrations or failovers regardless of how this flag is set.

Replication owners and visibility

So what about managed services and how is that affected by all of this? Not only do these permissions play an important role in the provider being able to see vSphere virtual machines, but there is an additional factor thrown into the mix. That factor is owner. When operating in a self-service model, the tenant who created the replication will also be the owner of the replication, so visibility is not impacted. But in the case of a managed service, the person who created the replication is the service provider, or the system administrator. Since the service provider created the replication, they are also the owner of the replication.

What this means is that the tenant, will not have the appropriate permissions to see vCloud Availability replications at the system level.

So how do we fix this so that the tenant can see the replications and allow the service provider to still manage the services? We can resolve this by assigning ownership of the replication to the tenant.

Won’t reassigning ownership impact the provider’s visibility? Remember, the service provider is a super user so they operate at the system level and can see across all tenants.

To make the change, select the replication(s) you would like to reassign. Next, click owner in the toolbar. This will bring up a modal with all of the available tenants this can be reassigned. Select the tenant to be assigned as owner. Finally, click Select to reassign ownership.

Once this is complete, not only does the service provider have visibility of the replication, but the tenant can now monitor and manage the replication as well.

Conclusion

It is important for not only the service provider, but the tenant to be aware of what controls are in place to control access. For customer who want limited access, they can force all replications to be instantiated from vCenter, but these replications can be managed from vCenter or vCD. In the case of service providers who are providing managed services, it will be important to not only ensure that Allow Cloud Access is enabled. Once replications have been established on behalf of the customer, it will be important for the provider to reassign the replications to the tenant so that they have visibility into the replication configuration and status.

Additional Resources

The post vCloud Availability 3.0 Blog Series: Cloud Access, Ownership, and Visibility appeared first on VMware Cloud Provider Blog.

Read Full Article

Read for later

Articles marked as Favorite are saved for later viewing.
close
  • Show original
  • .
  • Share
  • .
  • Favorite
  • .
  • Email
  • .
  • Add Tags 

Separate tags by commas
To access this feature, please upgrade your account.
Start your free month
Free Preview