Showing posts with label Cloud Computing. Show all posts
Showing posts with label Cloud Computing. Show all posts

Thursday, March 3, 2016

Microsoft Azure: Authentication and Authorization


Identity Management is one of the most important topic in cloud, especially in public cloud. This blog covers identity management for Microsoft Azure.

If you look at the customer that needs access to public cloud, there are three ways it can access cloud or we can say there are three types of customers: Large enterprise, small enterprise and someone working from home and accessing Azure.

lets start explaining each one of them
Large Enterprises: Integrating a Subscribers Own Identity Mechanism



uA large enterprise subscriber, authenticate with  own identity provider (step 1), in this case Active Directory Federation Services (ADFS).
uAfter successfully authenticating a user, ADFS issues a token. The client browser forwards the token to the Azure  federation provider that trusts tokens issued by customer’s ADFS (step 2) and,
u if necessary, performs a transformation on the Customers claims in the token into claims that  SAAS application recognizes (step 3) before returning a new token to the client browser.

uThe application trusts tokens issued by the Azure federation provider and uses the claims in the token to apply authorization rules (step 4). 


Small Enterprises:Providing an Identity Mechanism for Small Organizations
uA smaller company, authenticate with the Azure identity provider (step 1) because their own Active Directory can’t issue tokens that will be understood by the Azure federation provider.
uIf the Azure  identity provider can validate the credentials, it returns a token to the client browser that includes claims such as the user’s identity and the tenant’s identity. The client browser forwards the token to the Azure federation provider that trusts tokens issued by azure identity provider (step 2)
uIf necessary, performs a transformation on the Azure identity provider claims in the token into claims that SAAS Application recognizes (step 3) before returning a new token to the client browser.

uThe application trusts tokens issued by the Azure federation provider and uses the claims in the token to apply authorization rules (step 4).

 working from home and accessing Azure:Integrating with Social Identity Providers

ufederation provider is configured to trust tokens issued by a third-party identity provider, such as an identity provider that authenticates a Microsoft account or OpenID credentials. Ycompany plans to use Windows Azure Access Control to implement this scenario.
uWhen an individual user authenticates with his or her chosen identity provider (step 1), the identity provider returns a token to the client browser that includes claims such as the user’s identity.
uThe client browser forwards the token to the Azure federation provider that trusts tokens issued by the third-party provider (step 2) and
uIf necessary, performs a transformation on the claims in the token into claims that Azure application  recognizes (step 3) before returning a new token to the client browser.
uThe application trusts tokens issued by the federation provider and uses the claims in the token to apply authorization rules (step 4). When the user tries to access their surveys, the application will redirect them to their external identity provider for authentication.

Saturday, February 13, 2016

Nova Compute- Openstack


Above is the architecture of Nova Compute. Let me explain the above architecture  little bit

Nova-api: it accepts and responds to end user api calls

Nova-compute process is just a worker daemon that creates and terminates virtual machine instances via the hypervisor api's like VMware api

Nova-volume manages  the creation, attaching and detaching of z volumes to compute instances like Amazons elastic block storage.

Nova-network accepts networking tasks from the queue and then perform tasks to manipulate the network.( such as setting up bridge interfaces or changing ip tables now Neutron)

Nova-schedule process takes virtual machine  instance requests from the queue and determine where it should run, specifically which compute host it should run on

Queue ( RabbittMQ) provides a central hub for passing messages between daemons

SQL database stores most of the build-time and run-time state for cloud infrastructure



Thursday, February 11, 2016

Keystone – OpenStack Identity Service


Openstack Identity service is known as Keystone.. Keystone services for authenticating and managing user accounts and role information for our OpenStack cloud environment.Identity service is responsible for  the authentication and verification between all of OpenStack cloud services and is the first service that needs to be installed within an OpenStack environment. The OpenStack Identity service authenticates users and tenants by sending a validated authorization token between all OpenStack services. This token is used for authentication and verification so that one can use that service, such as OpenStack Storage and Compute. Therefore, configuration of the OpenStack Identity service must be completed first, consisting of creating appropriate roles for users and services, tenants, the user accounts, and the service API endpoints that make up the  cloud infrastructure.

Above diagram is an illustrates how identity service comes into production by following phased manner approach.

Installing Keyston – OpenStack Identity Service

We wont be covering configuration and commands in this blog. 
First you would need to create a controller node. in this controller node, you would need to install keystone and its back end Mariadb Database. Connect the two together and your server is ready

Once the keystone server is installed then we would need to create tenant, users and roles
A tenant in OpenStack is a project, and the two terms are generally used interchangeably.tenant has its own resources like users, images and instance as well as networks.Users can't be created without having a tenant assigned to them, so these must be created first. each user then needs roles to be assigned to them like admin role etc. 

Now we would need to define service endpoints. what is a service endpoint?
Each service in our cloud environment runs on a particular URL and port—these are the endpoint addresses for our services. When a client communicates with the  OpenStack environment that runs the OpenStack Identity service, it is this service that returns the endpoint URLs that the user can use in an OpenStack environment. To enable this feature, we must define these endpoints. In a cloud environment, we can define multiple regions. Regions can be thought of as different datacenters, which would imply that they would have different URLs or IP addresses. Opentsack identity service can be configured to service requests on 3 URLS:
1) Public URL: for end users
2)Admin URL: For administration
3)Internal URL: URl for behind the firewall, for private cloud


Now that the service endpoints are created, we can configure service endpoints so that our otherOpenStack services can utilize them. To do this, each service is configured with a username and password within a special service tenant. When setting up a service to use the OpenStack Identity service for authentication and authorization, we specify these details in their relevant configuration file.Each service itself has to authenticate with keystone in order for it to be available within OpenStack. Configuration of that service is then done using these credentials. 

Once its done you are done with identity service

Tuesday, February 9, 2016

VMware vRealize: Cloud Cost



VMware vCloud Suite contains these integrated products:
• Infrastructure Platform: VMware vSphere®: Industry leading server virtualization platform.
• VMware vRealize™ Operations™: Intelligent performance, capacity, and configuration management for vSphere environments.
• VMware vRealize Automation™: Self-service and policy-based infrastructure and application provisioning for vSphere environments.
• VMware vRealize Business™: Automated costing, usage metering, and service pricing of virtualized infrastructure for vSphere environments.
• Disaster Recovery Automation with VMware vCenter™ Site Recovery Manager™: Policy-based disaster recovery and testing for all virtualized applications.



The Overview dashboard provides a high-level overview of your Cloud cost and demands.
Click on Overview menu item to load the vRealize Business main dashboards.

This dashboard is divided into 3 columns:
  1. Total Cloud Cost - Total cost and cost per driver (component) with insight to Operation Expenses and Capital Expenses.
  2. Operational Analysis - Average cost per VM and cost of each compute resource.
  3. Consumption (Demand) Analysis - VM Count in your private Cloud and the distribution of costs between the Business Units based on their consumption.
The Operational Analysis tab provides a detailed overview on server costs. On the top of the screen you can see the current month cost and the monthly cost trend of each component. The pie chart on the right shows the percentage distribution of these components


The Comsuption Analysis tab details which resources each Business Unit consumes by VMs and Projects with breakdown to Compute resource.
You can now review the cost details of each BU clicking on Consumers List.

CLOUD COSTS DRIVERS

vRealize Business Standard categorizes the cost drivers into Server Hardware, Storage, Licensing, Maintenance, Labor, Network, Facilities, and Additional Costs. The cost driver data that you provide is the monthly cost except for the server hardware cost and storage array hardware cost.

MODIFYING PRIVATE CLOUD COSTS

You can modify the cost drivers of your data center. These costs can be in terms of percentage value or unit rate, and might not always be in terms of the overall cost. Based on your inputs, the final amount of cost drivers is calculated. If you do not provide inputs regarding cost drivers, the default values are taken from the reference database, which is part of the vRealize Business Standard product.
Click on Edit Cost
You can edit the total operating system licensing cost and VMware license cost of your cloud environment. You can edit the license cost by either selecting the ELA charging policy or selecting the per socket value.

SETTING UP PRICES FOR CLOUD SERVICES


You can set and edit the virtual machine price. You can define price manually or by creating policies based on vRealize Automation, vCloud Director, and vCenter Server categorization.
On the next steps you will understand how to edit cloud prices.
1. Click on Consumption Analysis menu item.
1. Click on Consumption Overview.
From now you are able to modify the Services pricing.
1. Click on Edit button
2. Click on Edit edit Pricing
You can select pricing mode whether you want define price manually or create policies to define the price, which enables to calculate virtual machine cost. You can define the price in two modes - Basic and Advanced. In Basic mode, you enter the price manually and in Advanced mode, you set the price by creating policies based on vRealize Automation, vCloud Director, and vCenter Server.

Friday, August 21, 2015

Amazon Web Services: Auto scaling and Cloudwatch


 In this blog, we will discuss Amazon Web Services: Auto scaling and Cloudwatch

The question is : What does Auto scaling provides?  The answer is:

  • Linear Horizontal Scaling 
  • HA

Second question is What Cloud watch enables? Cloud watch enables:

  • monitoring and alerting for resources
  • Alarms Can fire auto scaling policies, SNS notifications

 auto scaling, ELB and Cloud watch makes up what Amazon calls Triangle services

AUTO SCALING SET UP

To set up Auto scaling, we need to do the following things:

  • Create ELB( Its recommended but not necessary)
  • Create Instances in 2 or more AZs ( Its recommended but not necessary
              a) Create Launch Config: Launch config consists of
                          1) EC2 instance launch profile
                          2) Image ID (AMI)
                          3) Instance Type ( e.g t1.micro or m1.small)
                          4) key pair ( recommended)
                          5) Security Group
                          6) Name

  • Create Auto scaling Groups: In a auto scaling group you have AZs, Max or Min servers etc
  • Create Auto scaling Policy: The policy consists of buttons that an API/Scheduled/ cloudwatch can push
  • Create Cloud watch Alarms: Which can fire policies




CLOUD WATCH


Now we will briefly discuss cloud watch. So what does Cloud watch exactly do? Well, the answer is
  1. Monitors/Alarms on resources
  2. Basic Monitors provided free with most basic services ( EC2, ELB, SQS..etc)
  3. Alarms can fire auto scaling policies or SNS notifications
  4. cloud watch is statistics in , statistics out. below is an example














Cloud Watch alarms trigger when metric statistics goes in( or out  ) out of state for specific time

Hope it clears the functionality of cloud watch




Thursday, August 20, 2015

Amazon Web Services- Elastic Load balancer



In this Topic we will discuss Amazon Web services ELB or Elastic Load Balancers

So first question is : What does Load balancers Do?  The answer is:

  •  Send Traffic to many Back-end Servers
  • Attempt to evenly distribute load
  • Allows yours service to be elastic
  • It allows for Horizontal Scaling
  • Grow and shrink on demand
However,

Horizontal Scaling by the ELB in the cloud gives us:
  • Near Infinite Scaling
  • Huge cost savings
  • High Availability
  • Scaling By Tier
So what is Scaling by Tier? 

We can scale up or down web tier independent of APP Tier. This sis called scaling by tier

ELB Auto-scales ( Adds more IPs with increased traffic to the DNS)

ELB can also Terminate SSL, encrypt SSL to the back-end Machines

ELB also supports X-Forwarded-FOR

ELB has deep Integration with Auto Scaling and Cloud watch

Integration with Auto Scaling and Cloud watch

ELB can detect unhealthy Instances
  • Unhealthy by TCP or HTTP check
  • It automaticvally removes them dfrom scaling

However, Cloudwatch can add more instances behind ELB
  • Based on ELB metrics ( RequestCount, Latency and More)
  • Based on Instance Metrics (CPU. I/O, etc)


Remember,
  • Load balanced is first by Availability Zone
  • Then across instance in availability zone
  • ELB cost is static
  • ELB scaling is always reactive

Sunday, May 10, 2015

Building Microsoft Private Cloud Using System Center 2012: High Level design

Microsoft have a amazing private cloud solution besides its public cloud (Azure). In this blog we will cover how to build a Microsoft Private cloud. Lets face it, we are so much used to Microsoft.


If we see The picture above, you can clearly see Microsoft difference

Different componennents of System center:

  1)      Virtual machine manager
  2)      Operations manager
  3)      Configuration manager
  4)      Data protection manager
  5)      Orchestrator
  6)      Service manager

  7)      App controller

    The Flow is like below



But the architecture is



Private cloud is automating different stacks of technology. Thats what we are doing here.

for detailed implementation steps  please go to link

http://www.windowsnetworking.com/articles-tutorials/cloud-computing/building-private-cloud-system-center-2012-part1.html




Tuesday, April 28, 2015

Changing Cloud Market

In this blog we will cover changing face of cloud market.




Public cloud market is getting crowded. Now days everyone wants to provide public cloud services to the customers. The shake up has already started.

HP has declared that it is getting out of public cloud market. Wise decision.

Since the Cloud market thrives on razor thin margins, each VM costs Cents, it is increasing difficult for many vendors to survive in public cloud. Only the Big three Remains as dominant player: Google, Amazon and Microsoft.

Infrastructure as a service (IAAS) has now  high entry barrier. With huge investments and minimal returns, no new player can join the market.

So,

What other a players should do?

My thinking is that there is only few place where the money is right now in Cloud.

1) Software as a Service (SAAS): Now days anyone can go to public cloud and publish its COTS /custom application and give it as a service. SAAS has huge monetary benefits for software companies.

2) Application Transformation: There is a huge market in application transformation consulting. If the Organization wants to move its application to public or hybrid cloud environment, then it needs to make sure thats its application are cloud enabled. Application re-archeting, re-design and making them cloud enable is a goldmine.



So question is : Would you like to provide cloud services? If yes, then be prepared to provide something unique.

Wednesday, December 17, 2014

vCAC 6: Configuring IaaS-Tenants and Roles

This blog will cover configuring IaaS. In the last we learnt about IaaS installation

in this blog  we will discuss Tenants and Roles

A tenant is an organizational unit in a vCloud Automation Center deployment. When the system administrator configures single sign-on during the installation of VMware vCloud Automation Center, a default tenant is created. The default tenant includes a built-in  system administrator account to log in to the vCloud Automation Center console.If only one organizational unit is necessary for a deployment, the system administrator can then configure and use the default tenant.

There is a Division of Tenant and Non-Tenant Entities. Non-tenanted entities are visible and
consumable by all tenants. This means non-tenanted items like Build Profiles and Reservation
Policies are consumable in some tenanted objects, like blueprints.



To access the default tenant:
1.   Go to https://VCAC_Server_FQDN/shell-ui-app.

2.   Use the system administrator account(administrator@vsphere.local) to create additional tenants,
manage identity sources, and configure system roles.

In a single-tenant deployment, all configuration occurs in the default tenant. The tenant
administrators manage users and groups. The administrators also configure branding, notifications,
business policies, and catalog offerings.

In a single-tenant scenario, the system administrator and tenant administrator roles are typically
assigned to the same person, but the accounts are distinct. The system administrator account is
always administrator@vsphere.local, while the tenant administrator must be a user in one of the
tenant identity stores.

In a multitenant environment the system administrator creates new tenants for each organization:
Each tenant has a unique URL to access the vCloud Automation Center console:
    https://vcac_hostname/shell-ui-app/org/tenant_ URL_name
  • Tenant-level configuration for new tenants is segregated from the default tenant. 
  • Users with system-wide roles can view and manage configuration across multiple tenants.
A multitenant environment can be deployed in the following ways:
  • Default tenant-managed multitenancy
  • Individual tenant-managed multitenancy
Individual Tenant-Managed Multitenancy

In tenant-managed multitenancy, each tenant might have a dedicated infrastructure or use shared
infrastructure. Each tenant has IaaS administrators and fabric administrators that manage resources
for business groups in their own tenant.

Each tenant must be associated with at least one identity store. Identity stores can be OpenLDAP or Active Directory (AD). For a default tenant, you can also use AD in native mode.



System-Wide Roles

System administrator: The system administrator is typically the person who installs vCloud
Automation Center and is responsible for ensuring its availability for other users. 

Infrastructure (Iaas) administrator: The IaaS administrator is responsible for managing
endpoints and endpoint credentials, and creating fabric groups.

Fabric administrator: A fabric administrator is the administrator of one or more fabric groups.
Fabric administrators manage physical machines and compute resources in their groups, and
manage reservations and reservation policies associated with those resources. 

Tenant roles have responsibilities that are limited to a specific tenant, and cannot affect other tenants
in the system. Tenant roles are of the following types:
Tenant administrators: Tenant administrators are typically the business manager or IT administrator who is responsible for a tenant. Tenant administrators configure vCloud Automation Center according to the needs of their organizations. The responsibilities of tenant administrators include the following:
• User and group management.
• Tenant branding and notifications.
• Business policies such as approvals and entitlements.
• Tracking resource usage by all users in the tenant.
• Initiating reclamation requests for virtual machines.
• Managing business groups and shared blueprints in IaaS.

Approval administrator: An approval administrator has the ability to define approval policies.
These policies can be applied to catalog requests through entitlements that are managed by a
tenant administrator or business group manager.

Service Architect: This is role designation for the individuals who are responsible for creating
the blueprints for the catalog items that consumers can request from the service catalog

Business Group Manager: The business group manager is designated by the tenant administrator when creating or editing business groups. Manages one or more business groups. Typically a line manager or project manager. Business group managers manage catalog items and entitlements for their groups in the service catalog. 

• Support user: The support user is a role in a business group. Support users can request and
manage catalog items for other members of their groups. A support user is typically an executive administrator or department administrator.

• Business user: Any user in the system can be a consumer of IT services. Users can request
catalog items from the service catalog and manage their provisioned resources.

• Approver: As part of an approval policy, any user of vCloud Automation Center, for example, a
line manager, finance manager, or project manager can be designated as an approver

vCAC 6: Installation

In the last blog we covered pre-requisites of installation. Now we finally go ahead and do the installation

Lets Start with vCloud Automation Center Appliance Installation

To install the vCloud Automation Center appliance, we would need to accomplish below tasks:
1. Deploy the vCloud Automation Center virtual appliance.
2. Configure time settings.
3. Configure CAFE name.
4. Configure SSL certificates.
5. Configure SSO.

6. Type a license key


Deploy the vCloud Automation Center virtual appliance: We would need to deploy OVF or OVA template for this.

Now login to the appliance with root user id and password supplied at the time of installation. go to http://VCAC_Appliance_FQDN:5480/ 

Configure time settings
Go to admin tab and configure the time settings


Configure CAFE name

From Host Settings, select Resolve Host Name to set the CAFE host name


 Configure SSL certificates.


Configure SSO.




Type a license key


We have now completely installed VCAC appliance. Now we will do IAAS installation

To install the IaaS components:
1. Download the installation wizard from the vCloud Automation Center Appliance:
 http://VCAC_Appliance_FQDN:5480/installer
2. Validate prerequisite tests.
3. Select the installation type.
4. Type credentials.
5. Set service account details and passphrase.
6. Set configure database settings.
7. Configure DEM and agent names.


Now login to the appliance

Select the installation type.
• Complete Install will install all IaaS components on this machine.
• Custom Install allows an administrator to selectively choose IaaS components for a distributed installation.

Run Pre-requisite checker

now configure server and account settings
Confirm the name of the DEM Worker and the DEM Orchestrator. The endpoint name configured for the vSphere Agent is required when configuring endpoints.

Configure all the necessary settings for the component registry, SSO login, and the IaaS hostname

and you are done with installation. Next is configuration


Tuesday, December 16, 2014

vCAC 6: Installation Pre-requisites

Now we will discuss installation of vCAC 6.

Installation Pre-requisites:

vCloud Automation Center can be deployed in two Configurations:


  1. A minimal installation is the deployment of a single instance of each vCloud Automation Center component.
  2. distributed installation  installs multiple instances over separate servers for scalability, redundancy, high availability, and disaster recovery

vCloud Automation Center consists of the following components:

  •  Single sign-on (SSO) server : VMware Identity Appliance or VMware vCenter 5.5 U1 SSO
  • vCloud Automation Center appliance
  • VMware infrastructure as a service (IaaS)
  • Distributed Execution Managers (DEM)
  • Agents
We need to follow the below flowchart if we want to implement VCAC successfully




A vCloud Automation Center Appliance stores data in a PostgreSQL database. The default installation creates the PostgreSQL database locally but an administrator may install it on another server


The IaaS server supports the following database platforms:
Microsoft SQL Server
• SQL Server 2008 R2 SP1, SQL Server 2008 R2 SP2
- Enterprise, Standard, Express
• SQL Server 2012, SQL Server 2012 SP1
- Enterprise, Standard, Express
IaaS server database connectivity requirements:
TCP/IP protocol enabled for MS SQL Server
Microsoft Distributed Transaction Coordinator Service (MS DTC) enabled on all SQL nodes in the system Appropriate network ports open between Database Server and IaaS Server
If using SQL Server Express, the SQL Server Browser service must be running.


Ports

Identity Appliance ingress ports
Identity Appliance: Egress Ports


the remaining ports are


Now we need to determine compute requirements

component CPU Memory  Storage
Identity Server Virtual Appliance  1 2GB  2.5GB
vCloud Automation Center Appliance  2 8GB 30GB
IaaS Server  2 4GB 30GB
ITBM Standard  2 4GB 16GB
Application Director  2 4GB 16GB

Now we would need to determine IAAS service  manager requirements

The IaaS Manager Service requires the following:
  • .NET Framework 4.5 must be installed
  • Microsoft PowerShell 2.0 (included with Windows Server 2008 R2 SP1 and later) or Microsoft PowerShell 3.0 on Windows Server 2012 must be installed. SecondaryLogOnService must be running. Appropriate network ports between DEM host and Windows Server should be open.
Credentials:
We would also need to determine credentials for access.

  Credentials
vCenter service account A domain or local account is needed for endpoint access
Virtual appliance installation Administrative privileges on the deployment platform are required
IaaS installation The user that executes the installation should be a local administrator
IaaS database credentials The user must have IaaS database owner privileges
IaaS service user credentials The user must be a domain user and have local administrator privileges
on all systems with installed IaaS components





Now we are ready for Installation.


















Featured Post

Ichimoku cloud

Here how you read a ichimoku cloud 1) Blue Converse line: It measures short term trend. it also shows minor support or resistance. Its ve...