We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
FIWARE Lab: Upgrade to Community Account - FIWARE Forge Wiki

FIWARE Lab: Upgrade to Community Account

From FIWARE Forge Wiki

Jump to: navigation, search

To request for an account upgrade, FIWARE Lab users need to fill in an Upgrade Account request.

Contents

Who can apply?

  • Participants to the FIWARE Accelerator programme
  • Individuals and Companies willing to develop innovative applications based on FIWARE, and to disclose the usage of FIWARE they will make.

How much does it cost?

It's free! We are enacting this restriction to ensure that start-ups and SMEs willing to develop applications and demonstrators using FIWARE have the access to the proper resources.

How long do I retain the Community Status

The foreseen duration for the community status is 9 months. We believe this is enough to allow a team to develop a complete solution based on FIWARE. If needed, accounts can be extended. A procedure will be made available in due time.

How can i request for a Community Account upgrade

Users can apply through the help page (http://help.lab.fi-ware.org) clicking on the “Request Community Account upgrade” button, as displayed below.

Once clicked on the button, users can fill in the necessary informations:

  1. User Name (*): The full name of the person associated to the main account.
  1. User Account Email (*): The email associated to the main responsible person in the project.
  2. Are you already registered in FIWARE Lab?: Confirm that you created a main account for you project in FIWARE Lab. You should be able to register a “basic” account without any issue, if not contact the help desk.
  3. Company (*): The name of the company / university the main responsible person is associated with.
  4. Department: The department within the company / university the main responsible is associated with.
  5. Number of developers (*): the number of planned people involved in the project.
  6. FIWARE Accelerator Programme (*): if any, the accelerator that your project belongs to.
  7. Accelerator submission name: the name / code that you used to submit to the accelerator.
  8. Preferred FIWARE Lab Node (*): the FIWARE lab node where the application should be deployed. Predefined Nodes for accelerators are documented here: Reference Nodes Accelerators
  9. Already deployed (*): state if the application/project is already deployed (on the preferred node).
  10. Planned resources (*): description of the resources you need from the lab. e.g. i need 3 vm with 2 gb of ram and 3 cores
  11. Idea name (*): name of the project.
  12. Idea Description (*): description of the project, which GE are used, status, ...
  13. Proof of concept URL: pointer to a demo.
  14. Organization or additional accounts associated to the project (*): other accounts associated to the project or the main organization that need to access the main project. See Section 1.8 to find out how to retrieve the correct tenant id.

The image below, shows the form as displayed in the Help page.

How much should it take to complete the procedure?

The support team is available 9 am to 5 pm during working days. Except for complex request were negotiation on resources is required, a request should be fulfilled in 1 working day.

Quotas and Flavours

What is a flavour and what flavours are available?

Flavours represents the size of virtual machines. FIWARE Lab flavours are based on OpenStack flavours.

Available flavours in the Lab are listed in this table.

FIWARE Lab flavours
Flavour ID Flavour Name Memory User Disk Virtual CPUs
1 m1.tiny 512mb 1gb 1
2 m1.small 2048mb 20gb 1
3 m1.medium 4096mb 40gb 2
4 m1.large 8192mb 80gb 4

What are the default quotas?

  • VM Instances:2
  • VCPUs: 2
  • Hard Disk: 40 GB
  • Memory: 4096 MB
  • Public IP: 1

N.B.: Quotas may be subject to changes.

What are the default maximum quotas?

  • VM Instances: 5
  • VCPUs: 10
  • Hard Disk: 100 GB
  • Memory: 10240 MB
  • Public IP: 1

N.B.: Quotas may be subject to changes.

How do I get notified of the results of my application?

At each steps you will receive an email. By replying to the email you will be able to interact with the FIWARE Lab and provide additional informations that may be required.

Should you not receive any email, check your spam folder and if no message is found, please contact the general help desk: fiware-lab-help@lists.fi-ware.org. This screenshot provides and example of email notification.



How can authorize other users to use my cloud resources?

In the current resource assignment process to SMEs and Startups part of the FIWARE Accelerator programme, we assign resources (and community status) only to the main account. When developing with a team of people you may want to share your cloud resources with them. To add a basic or a community account to the accounts that can access your resources.

  1. Log in into your FIWARE Lab Account (https://account.lab.fiware.org).
  2. In the home page, switch to your account organization (account name cloud) using the upper right corner dropdown
  3. Go to the members tab (in the left side), and click “manage”.

  4. In the top left filter search, type the name of the user you want to add.
  5. Once the user appears in the result list, click on the plus sign next to the username.
  6. The user now appears linked to your organization and you can click on “save” to complete the procedure.
  7. Now you will see the user as a member of the org. Click "authorize" to give the needed roles inside Cloud application.
  8. In the top left filter search, type the name of the user you want to authorize.
  9. Once the user appears in the result list, click on the plus sign next to the username.
  10. Click in the dropdown of the user and add the role "Member" below "Cloud" application.
  11. Click on “save” to complete the procedure.
Personal tools
Create a book