MODIFICATION
70 -- Open Stack Based and Cloud Management Software
- Notice Date
- 2/16/2017
- Notice Type
- Modification/Amendment
- NAICS
- 511210
— Software Publishers
- Contracting Office
- Social Security Administration, Office of Budget, Finance, Quality and Management, Office of Acquisition and Grants, 1540 Robert M. Ball Building, 6401 Security Boulevard, Baltimore, Maryland, 21235, United States
- ZIP Code
- 21235
- Solicitation Number
- SSA-RFI-17-0227
- Archive Date
- 2/28/2017
- Point of Contact
- Rick Bolt, Phone: 410-966-8765
- E-Mail Address
-
rick.bolt@ssa.gov
(rick.bolt@ssa.gov)
- Small Business Set-Aside
- N/A
- Description
- Overview The Social Security Administration's Office of Hardware Engineering (OHE) is researching fully integrated and vendor supported OpenStack based private cloud suites to be used by OHE to build an on-premise self-managed private cloud. The proposed solution must also include a Cloud Management Platform to enhance the provisioning, automation, analysis, reporting, costing and management capabilities of the OpenStack suite. The main objectives of implementing this product will be to create a self-service virtual machine (VM) provisioning portal, automate common administrative tasks like VM creation, recoup unused resources, and infrastructure maintenance tasks as well as implement reporting like capacity analysis, utilization reports, and end-user costing. This Request For Information is to determine the market availability of an OpenStack based software package and Cloud Management Platform to meet the requirements outlined below. OHE requests that vendors interested in having their product included in the evaluation process indicate their product's compliance with each requirement individually. The responses to each requirement should be Fully Compliant, Partially Compliant, Non-Compliant or indicate an anticipated future release date of the product which will make it compliant. For all partial and non-compliant items, the vendor may at their discretion include an explanation of alternative solutions. OHE also requests a list of products included in the proposed solution and links to internet sites for additional product information. Product Requirements: The solution proposed must provide the following features and functionality. A. OpenStack Requirements - For the following requirements, vendors must provide a brief description of the components used to satisfy each item. I. Dashboard - Horizon or other OpenStack web-based graphical interface used to view, create and manage the OpenStack infrastructure and managed resources. II. Identity Management - Keystone or other OpenStack API-based authentication products capable of authenticating users in a multi-tenant environment. The solution must be capable of integrating with Active Directory for authenticating credentials. III. Compute - Nova or other OpenStack compute service capable of providing scalable, on-demand, self-service access to compute resources for the creation of virtual machines. IV. Network - Neutron or other OpenStack network management component capable of integrating into a Cisco Application Centric Infrastructure fabric for network configuration and management in the cloud environment. V. Block Storage - Cinder or other OpenStack block storage management component capable of accessing block storage in a CEPH environment. VI. Object Storage - Swift or other OpenStack object storage component capable of managing object storage in a CEPH environment. VII. Orchestration - Heat or other OpenStack orchestration component capable of automating the deployment and management of OpenStack resources including compute, storage and networks. VIII. Telemetry - Ceilometer or other OpenStack component capable of gathering and reporting infrastructure and virtual machine utilization metrics. IX. Image Repository - Glance or other OpenStack component capable of providing a catalog for storing and querying virtual disk images for use in the OpenStack environment. X. Infrastructure deployment 1. The solution must provide an automated solution for an OpenStack infrastructure deployment. 2. The solution must be capable of deploying the required operating system and software components to bare metal servers and configure each server to serve its intended role in the infrastructure (compute, management, network and storage nodes). 3. The solution must be capable of integrating the OpenStack components listed in items "A.I" through "A.IX" above to ensure proper configuration and functionality. 4. The solution must also provide a means of adding new nodes to the environment based on prior configuration information. XI. The solution must provide a process for upgrading the infrastructure components (compute, management, network and storage nodes) when moving to newer versions of OpenStack. For example, if OHE implements OpenStack version 8 then wants to move to OpenStack version 9, this process would require doing a "rip and replace method" of uninstalling all old software and reinstalling all new software when using the community supported version. This requirement would require the vendor provide a means of upgrading the software to the newer versions of any OpenStack component provided in this solution. XII. The solution must be capable of being fully hosted and managed within SSA's data centers and managed by SSA staff. B. Cloud Management Platform (CMP) Requirements - The following requirements include functionality OHE has determined to be necessary, but beyond the native capabilities of a pure OpenStack solution and must be supplemented by additional software. Please describe what solution the vendor proposes to meet the following requirements. I. Self-service Portal 1. A web-based portal for end users to request and provision virtual resources without assistance from an infrastructure administrator. 2. Portal must allow end-users to manage and modify virtual machine resources (VM) (e.g. virtual CPU, RAM and storage) of virtual machines previously provisioned. 3. Portal authentication of users must be integrated with Active Directory II. Unified Service Catalog 1. Customizable menu-driven catalog providing users access to request all available services from one location. 2. Available services must be customizable, providing a unique set of options depending on the user, group or role permissions. 3. Services available from multiple sites and infrastructures must be accessible from one location. III. VM Life Cycle Management 1. Solution must provide the capability to manage the entire life cycle of the VM including provisioning, configuration, power on/off, Console access, resource management (memory, cpu, storage), snapshot management and deletion. 2. Provide functionality to set leases and expiration times on provisioned machines to allow unused resources to be reclaimed automatically. IV. Configuration and Change Management 1. Solution must provide the ability to manage and deploy custom machine configurations for various customer groups, workloads or business units. 2. Solution must support multi-level approval workflows for machine provisioning and change requests 3. Solution must keep a complete history of all provisioned and available resources that can be referenced and reported on. V. Orchestration 1. Solution must provide a platform to use pre-built and customized workflows and scripts to automate any VM deployment and customization task and integrate them seamlessly into the self-service provisioning process 2. Solution must provide a platform to use pre-built and customized workflows and scripts to automate infrastructure administrative task. 3. Solution must provide an extensible architecture to allow the solution to connect to, pull data from and send data to external applications (Ticketing, Monitoring, Change Management, etc). 4. Solution must be built upon an open API architecture VI. Performance Monitoring 1. Solution must be capable of presenting to the end user health and resource utilization metrics of their managed resources. 2. Solution must be capable of presenting to infrastructure administrators intelligent monitoring and alerting functionality for infrastructure and provisioned machines to assist in troubleshooting and root cause analysis. 3. Solution must provide a mechanism for detecting failed hosts (compute nodes) in the OpenStack environment, determine the virtual machines impacted by the failed host and restart those impacted virtual machines on a functioning host. VII. Charge Back 1. Solution must provide functionality for administrators to assign costing metrics to resources including CPU, memory and storage 2. Based on the costing metrics assigned to resources, the solution must be able to generate reports detailing the cost associated with the resources consumed by each customer VIII. Capacity Planning 1. Solution must provide integrated tools for analysis of the infrastructure and currently consumed resources to predict future requirements for resources including cpu, memory, and storage. IX. Asset Management 1. Solution must maintain a complete inventory of all physical and virtual resources in the infrastructure. X. Multi-Tenancy 1. Solution must allow various customer groups or business units to provision isolated lab/development workloads on the same shared resources using the same unified portal without affecting the underlying production environment. 2. Each tenant (customer groups, workloads or business units) must be able to have unique options available to them in the unified service portal. (e.g. custom templates, custom service catalog, access restrictions). These unique settings should be available based on the group and not globally accessible or visible to all users. 3. Solution must restrict tenant groups to view and manage only their provisioned and assigned VMs and resources 4. Solution must be allow infrastructure administrators to select between viewing provisioned machines grouped per customer group or collectively in a single view. XI. Security 1. Solution must support Active Directory integration and Active Directory-Enabled Single Sign-on authentication. 2. Solution must support role-based security profiles for complex permission assignments of AD users and groups. 3. Granular permissions must apply from the top-level of the infrastructure down to a per-vm basis. XII. Detailed Reporting 1. Solution must provide built-in and customizable reports on hardware/software health, user/groups, and resources management 2. Solution must provide built-in and customizable reports on all aspects of managed infrastructure including hardware/software health, costing, user/groups, and resources management The following section include questions related to the proposed solutions. The questions do not indicate additional requirement of the solutions proposed, but will be used to help OHE evaluate additional considerations related to the implementation of various solutions available in the market. C. Questions related to the proposed OpenStack solution I. Does the proposed solution require the purchase of any vendor/manufacturer specific hardware? For example, is SSA required to purchase "Vendor X" servers, storage and/or network switches? If so, please provide a list of or link to a list of equipment required for the various infrastructure components (compute, storage, control, management, network...) II. Describe the licensing/support model for the solution? For example, are there entitlements per host, socket, RAM, per VM, per GB of storage and any other metered service? III. Does the vendor offer additional engineering/design, implementation and training services? IV. What Linux distribution(s) is the proposed solution based on (Red Hat, Ubuntu, CentOS...)? V. Does the vendor require remote access to the equipment for the purpose of monitoring or managing any part of the solution? Provide information on any requirements. VI. If remote access for monitoring and management is not required, does the vendor offer such a service as an option if the customer wants this level of service? Provide information about services offered. D. Questions related to the proposed CMP I. Describe the licensing/support model for the CMP solution? For example, are there entitlements per host, socket, RAM, per VM, per GB of storage and any other metered service? II. Is support for the proposed OpenStack and CMP solutions offered by the same vendor via common support channel (telephone, web requests)? III. What hypervisors can the CMP manage (OpenStack, RHEV, VMware, KVM...)? IV. Is the CMP capable of providing the same level of service for deploying to and managing resources in public cloud environments (AWS, Azure...)? If so, what cloud environments are supported? Describe any limitations related to management capabilities similar to items "B.I." through "B.XII." in a public cloud environment. V. What is the maximum number of unique tenants or tenant groups that can be managed by the CMP? VI. Does the CMP offer visibility into and/or management of Platform as a Service (PaaS) infrastructures for the purpose of reporting on PaaS resource utilization (e.g. number of containers, number of nodes and resources consumed)? VII. Does the CMP have the capability to perform patching/updates/upgrades to the OpenStack infrastructure components and managed virtual machines? VIII. Does the CMP expose APIs that can be used by other applications to automate functions normally done within the GUI, including VM creation, deletion, change, power on/off, VM and resource utilization metrics gathering and tenant management? VENDOR RESPONSES: Interested firms with the capability of providing the requirement shall submit capability statements that demonstrate their expertise in the above-described areas in sufficient detail, including any other specific and relevant information, so the Government can determine the firm's experience and capability to provide the requirements. Failure to demonstrate the capability of providing the requirement in response to this market survey may affect the Government's review of the industry's ability to perform or provide these requirements. In addition to capability statements, firms must include this information in their responses: 1) organization name, address, email address, website address, and telephone number; 2) size and type of ownership and socioeconomic designation for the organization [i.e. small business, small disadvantaged business, 8(a), women-owned small businesses, veteran-owned small businesses, service disabled veteran-owned small businesses, Historically Underutilized Business Zone small businesses, etc.]; 3) availability of products and services are available on the GSA schedule; and 4) business experiences. You may submit product cost and/or pricing data, inclusive of annual maintenance, with your response, however it is not required. Respondents should refer to SSA-RFI-17-0227. Electronic responses only must be submitted by 12:00 PM, ET, February 27, 2017 to the email address below. Faxed information will not be permitted. The size limitation for email attachments is 5 megabytes. NO FORMAL SOLICITATION IS BEING ISSUED AT THIS TIME, and the Government does not intend to pay for the information submitted. This information will be used in SSA's assessment of capable sources. Respondents will not be notified of any evaluated results from the data received. Any questions should be submitted via EMAIL ONLY (no phone calls please) to the Contract Specialist at Rick.Bolt@ssa.gov
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/SSA/DCFIAM/OAG/SSA-RFI-17-0227/listing.html)
- Place of Performance
- Address: SOCIAL SECURITY ADMINISTRATION, 6401 SECURITY BLVD., Baltimore, Maryland, 21235, United States
- Zip Code: 21235
- Zip Code: 21235
- Record
- SN04406398-W 20170218/170216235651-d31a452e60c2cbb9d9e2ce9533124453 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |