45
I Use This!
Activity Not Available

News

Analyzed about 1 month ago. based on code collected about 2 months ago.
Posted about 19 hours ago by Lars Kellogg-Stedman
It's a bit of an embarrassment when you submit a review to Gerrit only to have it fail CI checks immediately because of something as simple as a syntax error or pep8 failure that you should have caught yourself before submitting...but you forgot to run your validations before submitting …
Posted about 19 hours ago by Simon Decaestecker
Episode 48 : ONLYOFFICE ONLYOFFICE is an online office suite permitting you to create and edit your files directly through an internet browser. In this way, you can edit your files (compatible with Microsoft Office) collaboratively and in real ... [More] time without any other software, thats improves the security, and in the case of a company, manage some projects and their achievement and a client database for example. Your emails can be read with ONLYOFFICE and, if you have your own domain name, you can use it. Preparations The Versions CoreOS Stable 1185.5 ONLYOFFICE 8.9.1.191 The prerequisites to deploy this stack These should be routine by now: An Internet access A Linux shell A Cloudwatt account with a valid keypair The tools of the trade: OpenStack CLI A local clone of the Cloudwatt applications git repository (if you are creating your stack from a shell) Size of the instance By default, the stack deploys on an instance of type “Standard 2” (n1.cw.standard-2). A variety of other instance types exist to suit your various needs, allowing you to pay only for the services you need. Instances are charged by the minute and capped at their monthly price (you can find more details on the Pricing page on the Cloudwatt website). Stack parameters, of course, are yours to tweak at your fancy. By the way… If you do not like command lines, you can go directly to the “run it thru the console” section by clicking here What will you find in the repository Once you have cloned the github, you will find in the blueprint-coreos-onlyoffice/ repository: blueprint-coreos-onlyoffice.heat.yml: HEAT orchestration template. It will be use to deploy the necessary infrastructure. stack-start.sh: Stack launching script. This is a small script that will save you some copy-paste. stack-get-url.sh: Flotting IP recovery script. Start-up Initialize the environment Have your Cloudwatt credentials in hand and click HERE. If you are not logged in yet, you will go thru the authentication screen then the script download will start. Thanks to it, you will be able to initiate the shell accesses towards the Cloudwatt APIs. Source the downloaded file in your shell. Your password will be requested. $ source COMPUTE-[...]-openrc.sh Please enter your OpenStack Password: Once this done, the Openstack command line tools can interact with your Cloudwatt user account. Adjust the parameters With the blueprint-coreos-onlyoffice.heat.yml file, you will find at the top a section named parameters. The sole mandatory parameter to adjust is the one called keypair_name. Its default value must contain a valid keypair with regards to your Cloudwatt user account. This is within this same file that you can adjust the instance size by playing with the flavor parameter. heat_template_version: 2015-04-30 description: Blueprint ONLYOFFICE parameters: keypair_name: description: Keypair to inject in instance label: SSH Keypair type: string flavor_name: default: n1.cw.standard-2 description: Flavor to use for the deployed instance type: string label: Instance Type (Flavor) constraints: - allowed_values: - n1.cw.standard-2 - n1.cw.standard-4 - n1.cw.standard-8 - n1.cw.standard-12 - n1.cw.standard-16 volume_attachment: description: Attacher un volume cinder de 20GO ? default: 0 type: string [...] Start stack In a shell, run the script stack-start.sh with his name in parameter: ./stack-start.sh ONLYOFFICE +--------------------------------------+-----------------+--------------------+----------------------+ | id | stack_name | stack_status | creation_time | +--------------------------------------+-----------------+--------------------+----------------------+ | ee873a3a-a306-4127-8647-4bc80469cec4 | ONLYOFFICE | CREATE_IN_PROGRESS | 2015-11-25T11:03:51Z | +--------------------------------------+-----------------+--------------------+----------------------+ Within 5 minutes the stack will be fully operational. (Use watch to see the status in real-time) $ watch heat resource-list ONLYOFFICE +------------------+-----------------------------------------------------+---------------------------------+-----------------+----------------------+ | resource_name | physical_resource_id | resource_type | resource_status | updated_time | +------------------+-----------------------------------------------------+---------------------------------+-----------------+----------------------+ | floating_ip | 44dd841f-8570-4f02-a8cc-f21a125cc8aa | OS::Neutron::FloatingIP | CREATE_COMPLETE | 2015-11-25T11:03:51Z | | security_group | efead2a2-c91b-470e-a234-58746da6ac22 | OS::Neutron::SecurityGroup | CREATE_COMPLETE | 2015-11-25T11:03:52Z | | network | 7e142d1b-f660-498d-961a-b03d0aee5cff | OS::Neutron::Net | CREATE_COMPLETE | 2015-11-25T11:03:56Z | | subnet | 442b31bf-0d3e-406b-8d5f-7b1b6181a381 | OS::Neutron::Subnet | CREATE_COMPLETE | 2015-11-25T11:03:57Z | | server | f5b22d22-1cfe-41bb-9e30-4d089285e5e5 | OS::Nova::Server | CREATE_COMPLETE | 2015-11-25T11:04:00Z | | floating_ip_link | 44dd841f-8570-4f02-a8cc-f21a125cc8aa-`floating IP` | OS::Nova::FloatingIPAssociation | CREATE_COMPLETE | 2015-11-25T11:04:30Z | +------------------+-----------------------------------------------------+-------------------------------+-----------------+---------------------- The start-stack.sh script takes care of running the API necessary requests to execute the normal heat template which: Starts an CoreOS based instance with the docker container ONLYOFFICE Document Server, the container ONLYOFFICE Mail Server and the container ONLYOFFICE Community Server Expose it on the Internet via a floating IP. All of this is fine, but… You do not have a way to create the stack from the console? We do indeed! Using the console, you can deploy ONLYOFFICE: Go the Cloudwatt Github in the applications/blueprint-coreos-onlyoffice repository Click on the file named blueprint-coreos-onlyoffice.heat.yml Click on RAW, a web page will appear containing purely the template Save the file to your PC. You can use the default name proposed by your browser (just remove the .txt) Go to the « Stacks » section of the console Click on « Launch stack », then « Template file » and select the file you just saved to your PC, and finally click on « NEXT » Name your stack in the « Stack name » field Enter the name of your keypair in the « SSH Keypair » field Choose your instance size using the « Instance Type » dropdown and click on « LAUNCH » The stack will be automatically generated (you can see its progress by clicking on its name). When all modules become green, the creation will be complete. You have to wait 5 minutes to the softwares be ready. You can then go to the “Instances” menu to find the floating IP, or simply refresh the current page and check the Overview tab for a handy link. If you’ve reached this point, you’re already done! Go enjoy ONLYOFFICE! A one-click deployment sounds really nice… … Good! Go to the Apps page on the Cloudwatt website, choose the apps, press DEPLOY and follow the simple steps… 2 minutes later, a green button appears… ACCESS: you have your ONLYOFFICE. Enjoy Once all this makes you can connect on your server in SSH by using your keypair beforehand downloaded on your compute, You are now in possession of ONLYOFFICE, you can enter via the URL http://ip-floatingip. Your full URL will be present in your stack overview in horizon Cloudwatt console. After you gave informations about the administrator, you arrive on the interface: You can now use your office suite, this one being hosted in France in a safe environment, you can completely trust on this product. So watt? The goal of this tutorial is to accelerate your start. At this point you are the master of the stack. You now have an SSH access point on your virtual machine through the floating-IP and your private keypair (default userusername core). You have access to the web interface via the address specified in your output stack in horizon console. Here are some news sites to learn more: http://www.onlyoffice.org/ http://helpcenter.onlyoffice.com/ Have fun. Hack in peace. [Less]
Posted about 19 hours ago by Jason Baker
Explore what's happening this week in OpenStack, the open source cloud computing project.
Posted about 19 hours ago by hugh
Introduction Welcome to Last week on OpenStack Dev (“Lwood”) for the week just past. For more background on Lwood, please refer here. Basic Stats for the week 16 to 22 January for openstack-dev: ~485 Messages (down about 15% relative to the long term average) ~164 Unique threads (down about 8% relative to the long term average) […]
Posted about 19 hours ago by Alin Băluțoiu
before reading the conclusions, we recommend to read the previous posts in this series if you want to know more details about the environment and the test scenarios: Introduction, Scenario 1, Scenario 2, Scenario 3.   Conclusions It’s time to discuss ... [More] all the results obtained so far. The table below show the average time expressed in seconds… The post OpenStack Newton Benchmarking – Conclusions appeared first on Cloudbase Solutions. [Less]
Posted about 19 hours ago by bmwiedemann
This post it to document how we setup cloud.suse.de which is one of our internal SUSE OpenStack Cloud deployments for use by R&D. In 2016-06 we started the deployment with 4 nodes. 1 controller and 3 compute nodes that also served for ceph (distributed storage) with their 2nd HDD. Since the nodes are from 2012 […]
Posted about 19 hours ago by OpenStack Superuser
Posted about 19 hours ago by Nicole Martinelli
OpenStack Hackathons are a fast and furious weekend of work that rewards the best projects with fantastic prizes, here's how you can plan one. The post Ready, set, code: Make your hackathon happen appeared first on OpenStack Superuser.
Posted about 19 hours ago by slagle
In a previous post, I talked about using TripleO with already deployed and provisioned servers. Since that was published, TripleO has made a lot of progress in this area. I figured it was about time for an update on where the project is with this feature. Throughout the Ocata cycle, I’ve had the chance to • Read More »
Posted about 19 hours ago by doug
Last week I spoke at the Atlanta OpenStack meetup about “Driving OpenStack via Ansible,” in which I introduced Ansible as a tool and talked about its ability to integrate with OpenStack. As part of the presentation I used two playbooks to launch VMs ... [More] on a cloud and configure them with different applications. We walked through … Continue reading Driving OpenStack via Ansible [Less]