- Freely download the code, run it unattended in your premises without the need to sign a non-disclosure agreement
- Discuss what you think about that on a dedicated forum
- Watch demonstrations of IBM SmartCloud Provisioning capabilities in the work and tell us if you like or do not like the newest features just clicking a button.
- Join our community to get early access to and provide feedback on cloud provisioning and orchestration technologies
- Stay tuned to the community to hear the latest new on available code drops and functionalities
- Play with the product in our premises joining the hosted beta. To access the hosted beta, send an email to email@example.com
rossella 120000Q98F Marcações:  isaac beta smartcloud cloud demo provisioning 8.143 Visualizações
The open beta program for the upcoming IBM SmartCloud Provisioning release started:
cynthyap 110000GC4C Marcações:  virtualization cloud_computing provisioning cloud smartcloud 4.516 Visualizações
Today IBM announced new SmartCloud Foundation capabilities to help organizations realize the potential of cloud computing. Watch the replay of the IBM SmartCloud launch webcast, to learn more about how the new announcements, including IBM SmartCloud Provisioning (delivered by IBM Service Agility Accelerator for Cloud), can help customers move beyond virtualization to more advanced cloud deployments.
Birgit.Nuechter 270001WHA9 Marcações:  provisioning openstack cloud patterns smartcloud orchestrator 9.983 Visualizações
IBM SmartCloud Orchestrator, the first new private cloud offering based on OpenStack and other cloud standards, is now available. Users are looking for Cloud solutions that increase agility, cost savings and offer a competitive advantage. IBM SmartCloud Orchestrator exceeds those needs:
Get started today!
SmartCloud Orchestrator Analyst and PressCoverage:
rossella 120000Q98F Marcações:  provisioning demo cloud icon library image iaas virtualization smartcloud accelerator management 11.410 Visualizações
As part of the transparent development initiative, IBM SmartCloud Provisioning (formerly known as IBM Service Agility Accelerator for Cloud) launches a series of daily demos, starting from November 7th. Every session will take about one hour.
In this way you can have a look in almost real time at what is happening in IBM SmartCloud Provisioning development, learn about new and enhanced capabilities.
If you are interested in joining the sessions, here is the schedule in Central European Time (CET):
The sessions will be focused on image management.
No password is required
Birgit.Nuechter 270001WHA9 Marcações:  orchestrator smartcloud forum cloud 1 Comentário 7.838 Visualizações
I am pleased to announce that we have a new public forum for SmartCloud Orchestrator where users can discuss technical topics related to the product and address questions they might have.
SmartCloud Orchestrator has just been released. It is IBM's new private cloud offering based on OpenStack and other cloud standards.
This forum is a discussion platform and does not replace the IBM support. I hope you find this forum useful and it helps in the formation of an online user community.
Birgit Nuechter, Field Quality Manager for IBM SmartCloud Orchestrator
IBM SmartCloud Provisioning 2.1.0 Fixpack 1 has been released at the end of November.
This fixpack adds support for zLinux as managed-to platform and include a few enhancements in the network segregation space, image management, ldap management
A few more details about enhancements:
The fixpack can be installed as an update on top of your existing IBM SmartCloud Provisioning 2.1 installation or as a fresh new installation.
You can download it from http://www.ibm.com/support/fixcentral
Are you a cloud addicted?
Do you want to be always updated on the latest technologies?
Do you want to contribute to development decisions in the IBM SmartCloud Provisioning world?
Are just curios to see what's cooking in IBM SmartCloud Provisioning development?
If you answered "yes", have a look at the Upcoming Feature page in the IBM SmartCloud Provisioning WIKI.
It starts getting populated with recorded demos and screenshots showing what is currently into the developers'mind.
Each page is equipped with a set of buttons to immediately and easily provide your feedback directly to the development team.
More ideas, thoughts, videos will be added shortly on the same page, so stay tuned!
...Just do not get lazy, click the links!!!
cynthyap 110000GC4C Marcações:  cloud-computing provisioning cloudops cloud cloud-monitoring devops cloud_computing smartcloud smartcloudprovisioning 7.743 Visualizações
DevOps has become something of a buzzword lately but the idea behind it can be truly powerful. Using a combination of technology and best practices to increase collaboration between development and operations teams can accelerate the application development lifecycle while improving software quality and reducing costs.
For many, the development process has become more complex and segregated from operations. Factors such as inefficient communications, manual processes and poor visibility into the deployment process result in production bottlenecks as well as subpar quality throughout the development and delivery cycle.
To address these challenges, organizations have often turned to adhoc and siloed efforts. And so gaps still exist due to lack of integration across people, processes and tools. The reality is that an effective DevOps solution requires an integrated approach of continuous delivery that optimizes and accelerates the application lifecycle in every phase: development, testing, staging and production.
What this means is that changes made in development are continuously built, integrated and tested for function, performance, systems verifications, user acceptance, and then staged, ready for production. And it can all be brought together through an integration framework that can automate the individual tasks across the various stages of the pipeline and continuously deliver changes, providing end-to-end lifecycle management. Continuous automation is necessary in the following key areas:
• Continuous integration provides faster validation and delivery of code changes via automated, repeatable execution of build processes with continuous feedback
• Continuous deployment provides on-demand environment configuration and the ability to continuously deploy code and configuration middleware.
• Continuous testing automates testing in production-like environments.
• Continuous monitoring increases visibility into application performance and provides data to trace and isolate product defects.
With an automated process for moving application changes through progressively richer test environments that mirror the production environment, chances for error and roll back are greatly reduced.
The result is increased visibility into the delivery pipeline, standardized communication between Dev and Ops and more efficient and accurate delivery of software projects. And the delivery process can scale dynamically as business needs grow.
Here’s how IBM is addressing DevOps, with the launch of SmartCloud Continuous Delivery--an agile, scalable and flexible solution for end-to-end lifecycle management that allows organizations to reduce software delivery cycle times and improve quality. SmartCloud Continuous Delivery is also available on Jazz.net.
SandraWeiss 060000BCJJ Marcações:  kvm vmware virtualization monitoring esxi health smartcloud_health solutions provisioning smartcloud cloud 1 Comentário 8.807 Visualizações
Service Health for IBM SmartCloud Provisioning has officially GA'ed and is now available on IBM Integrated Service Management Library ( ISML ).
Service Health provides pre-built integrations between IBM SmartCloud Provisioning and IBM SmartCloud Monitoring utilizing a custom agent, OS agents, and the ITMfVE agents. A product provided navigator offers a concise overview on the health of the IBM SmartCloud Provisioning infrastructure enabling the ability to identify and react to issues in your environment quickly minimizing the impact, such as an unresponsive compute node, high disk usage on storage nodes or key kernel services not responding. It also provides visibility into the KVM and ESXi hyper-visors.
This solution can be downloaded from the IBM Integrated Service Management Library( ISML ) following this link -> Service Health for IBM SmartCloud Provisioning
rossella 120000Q98F Marcações:  smartcloud beta isaac demo provisioning cloud 6.344 Visualizações
A presentation and demo session for IBM SmartCloud Provisioning held on thursday, April 26th at 3:00 PM central european time (CET)
The presentation will be around architectural changes in IBM SmartCloud Provisioning.
The demo will be about registering High Scale Low Touch as cloud group in IBM SmartCloud Provisioning.
No password is required
rossella 120000Q98F Marcações:  isaac smartcloud beta provisioning download 4.841 Visualizações
A new beta drop for IBM SmartCloud Provisioning is available.
Here below you can see the list of key functionalities included:
If you would like to try out the new features without the effort of installing the product, join the community and play with our hosted beta
If you would like to download the code, go here
One of the messages behind cloud computing is "pay-per-use": the adoption of a virtualized, standardized, self service and automated environment should come with the possibility to be charged only for the used resources.
IBM SmartCloud Provisoning comes with an idea of low complexity, low administration and ease of use.
Keeping these messages in mind, I was thinking at how to extract metering information. I had in mind something easy, doable also by people who definitely do not want to invest in programming, that does not need any modification to database tables to store historical data.
So I had a look at the available IBM SmartCloud Provisioning interfaces and I just found a couple of command line commands that could help me achieving my goal:
iaas-describe-resources-inuse-by-access and iaas-describe-accesses-by-user
The first command displays the number of images, cores and the amount of memory and disk space in use by a specific access ID. So this commands shows the key measures that in cloud computing are usually taken into consideration for usage and accounting.
The second command shows the relationship between access IDs and user IDs. This mapping helps in building metering information per user and not per access ID. In a simple environment the map is 1-1, but for example you may have the same user accessing more VM regions and so having multiple access IDs associated.
Given these two command, it is pretty straightforward to setup a couple of cronjobs/periodic tasks (depending if you would like to do it on Linux or on Windows) that with a predefined sequence ( for example once a hour) will extract this data and store it in a temporary file.
You can then have a another cronjob/periodic task that sums up all these information daily, per user, maybe adding your specific rate codes. If you choose to store this data for example in a CSV file, then you can easily import it into a reporting engine.
We're pleased to make available as a beta Service Health for IBM SmartCloud Provisioning. As this is a beta we welcome any and all feedback.
Service Health (Beta) for IBM® SmartCloud Provisioning provides prebuilt integrations between IBM SmartCloud Provisioning and IBM SmartCloud Monitoring. This solution allows you to easily monitor your IBM SmartCloud Provisioning infrastructure to identify and react to issues in your environment.
This solution is available via the IBM Integrated Service Management Library( ISML ). You can find it here -> Service Health for IBM SmartCloud Provisioning. Please use the "Comment or Review" link on that page to post feedback. You may also use the "Contact Provider" link as well.
AHUP_Gianluca_Bernardini 120000AHUP Marcações:  provisioning cloud bot decentralized smartcloud scale-out hslt p2p 6.370 Visualizações
SmartCloud Provisioning is designed to minimize the use of a centralized “command and control” approach, in favor of scale out management, where endpoints can participate in management activities and do not depend on a single configuration management database.
This allows SmartCloud Provisioning to handle multiple provisioning tasks in parallel, across an unlimited number of servers.
Cloud users can request deployments of virtual machines and have access to the provisioned systems in very few seconds, thanks to the parallel and distributed processing that happens transparently and under the covers.
Let’s drill down into the details about this distributed management approach.
SmartCloud Provisioning internally uses a peer to peer (P2P) messaging infrastructure to pass provisioning and management messages between agents, which contribute to the decentralized control.
Agents are installed on the compute nodes (i.e. the hypervisors) as well as on the storage nodes, where images and volumes reside.
The P2P connections between agents not only allow self-monitoring of their health in order to implement a low-touch management infrastructure, but also allow orchestrating the communications to achieve an effective load distribution and decentralized management of the requests performed by cloud users.
The P2P communication overlay is backed by a distributed lock service, which is based on ZooKeeper.
ZooKeeper is a distributed, open-source coordination service for distributed applications, which exposes a simple set of primitives that distributed applications can build upon to implement higher level services for synchronization, configuration maintenance, and groups and naming. It is designed to be easy to program, and uses a data model styled after the familiar directory tree structure of file systems.
Like the distributed processes it coordinates, ZooKeeper itself is intended to be replicated over a set of servers that must all know about each other. They maintain an in-memory image of state, along with a transaction logs and snapshots in a persistent store.
SmartCloud Provisioning agents connect to a single ZooKeeper server. Each agent maintains a TCP connection with the Zookeeper server, through which it sends requests, gets responses, gets watch events, and sends heart beats. If the TCP connection to the server breaks, the agent will connect to a different server.
When a deployment request is received by SmartCloud Provisioning, the request is processed by the Web Services layer, passed to the management infrastructure, and managed by the agents and the ZooKeeper services.
The following steps describe in more details the internal communications, as depicted in figure 1 below.
This processing happens in a transparent way for the end user, who just sees the deployment request being served in few seconds.
As I said, this processing happens under the covers in a very fast way and the user does not have to worry about any of the steps above.
This allows reaching high levels of parallelism, decentralized management, as well as scale-out capabilities that can be easily reached by increasing the number of servers.
If you're interested in trying the SmartCloud Provisioning distributed management capabilities, you can download a trial version from the following link:
marcese 11000065AG Marcações:  deployment rapid cloud isaac smartcloud image 7.841 Visualizações
I've been impressed by the speed of provisioning a set of virtual machines in just a few tens of seconds using IBM Smart Cloud Provisioning. In most cases you can get a running virtual machine in less than one minute.
The Smart Cloud Provisioning technology has been devised and particularly optimized for managing the following cloud infrastructure scenarios:
Many other workloads can be deployed and easily automated on top of Smart Cloud Provisioning. For example, traditional stateful applications can be easily deployed for simple HA solutions. Anyway you get the maximum performances from Smart Cloud Provisioning when operating in the context of the above scenarios.
To achieve such high performances Smart Cloud Provisioning has been designed focusing the attention to an optimized virtualization infrastructure based on OS streaming: no need to copy large image files over the network when provisioning.
Image copying is the single biggest bottleneck in VM provisioning today both in terms of CPU, memory, I/O and bandwidth usage. In traditional Cloud provisioning approaches all of this overhead is system resource that is just pure overhead (nobody builds a Cloud to provision systems - provisioning is an overhead that is required to have systems on which business workload is deployed, and any overhead is in conflict with the business workload).
The key element of such infrastructure are the so called ephemeral instances, that are virtual machines having no persistent state. Once they get terminated all the data associated with them is deleted as well. They are clones of a master image and these clones will have a primary virtual disk which is ephemeral: when the instance goes, so does its ephemeral storage (mechanisms exist in Smart Cloud Provisioning to provide persistence, if needed by some scenarios).
When creating a new instance, since master images are read-only resources and are replicated across the storage cluster, Smart Cloud Provisioning uses the Copy-on-Write (CoW) technology and the iSCSI protocol to stream them avoiding expensive copying. Each iSCSI session results in a valid block device to be created in the host OS. Of course each guest OS (corresponding to a given instance) requires a writable block device representing the main disk of the system. All supported hypervisors have a storage virtualization layer which includes the Copy-on-Write technology. For example, KVM's qcow2 files can be configured to implement CoW by referencing a backing storage device. VMWare has something called redo files which effectively do the same thing as well. In each case, the hypervisor can natively use the CoW file referencing the iSCSI block device to expose a virtual block device to the virtual machine. Depending on the hypervisor and guest OS this device will show up as something like /dev/sda or c:\. The CoW files are stored locally on the hypervisor's file system. When the instance is terminated, the Smart Cloud Provisioning agent will simply discard the CoW file and check if any other instances are using the same iSCSI device. If the device is no longer in use, the agent will also tear down the iSCSI device.
Thanks to the above infrastructure the action of provisioning a new virtual machine results in a very fast and reliable process that allows to create individual systems in tens of seconds and of peak requests of 1000s of systems per hour.
If you're interested in trying the Smart Cloud Provisioning product, you can download a trial version from the following link: