Giter VIP home page Giter VIP logo

f5-big-ip-cloud-edition-trial-quick-start's Introduction

BIG-IP Cloud Edition Trial Quick Start

Note: Looking for BIG-IQ 7.x releases? Check out this other git repository

F5 BIG-IP Cloud Edition: Automatically deploy pre-built app services dedicated to each application.

With F5 BIG-IQ Centralized Management (CM), you can securely manage traffic to your applications in AWS and Azure by using what F5 calls a Service Scaling Group (SSG).

From a centralized view, you can monitor the health and statistics of your applications as well as devices that are load balancing traffic and hosting applications. You can also set up alert thresholds to immediately notify you of certain events.

This CloudFormation Template (CFT) or Azure Resource Manager (ARM) creates two BIG-IQ VE instances:

  • a BIG-IQ Centralized Management (CM) instance to configure and orchestrate instances of BIG-IP VE
  • a BIG-IQ Data Collection Device (DCD) to store analytics data.

The templates also create an Apache demo web server.

After you configure the BIG-IQ instances, BIG-IQ automatically launches a BIG-IP VE instance in AWS or Azure.

Copyright

Copyright 2014-2019 F5 Networks Inc.

License

Apache V2.0

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Contributor License Agreement

Individuals or business entities who contribute to this project must have completed and submitted the F5 Contributor License Agreement.

f5-big-ip-cloud-edition-trial-quick-start's People

Contributors

bghalif5 avatar khous avatar rjouhann avatar vinaykumar0408 avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

valenswang sessin selhorn 1crowe javierjeronimo mirzawaqasahmed anibus

f5-big-ip-cloud-edition-trial-quick-start's Issues

Issue when I was creating one more application after created a new ELB on AWS

Hi,

I have deployed the infrasturcture by following your template successfully. However, after I tried to create one more Elastic load balancer on AWS and create a new application on the BIGIQ CE, it prompt out an error and said " there is an error during the deployment ".

Let say, if I would like to deploy one more application on BIGIQ CE and use the WAF per App VE license.
Other than creating the Service Scaling group again and make use of the AWS default https WAF template, any other important configuration did I miss which cause an error ?

AWS quick start creates AWS "cloud environment" without selecting AMI image

The AWS quick start will deploy the BIG-IQ and DCD successfully. But, the SSG fails. When I look at "Cloud Environment" section, the AMI Image type is blank. Meaning, the dropdown is still on "Select" which means no image is selected. As a result, it looks like the latest AMI is referenced in AWS which is currently ami-04e893bab1e8b9b10. This is running 14.0. Something with this image and/or version 14.0 breaks the SSG deployment.

As a fix, I created a new cloud environment and this time I made sure AMI had an image selected. I chose the 13.1.1 Best 1 boot slot. For reference, that ends up being image ami-58c3d327. This works successfully, and the SSG deployed correctly and shows an active state. This proves the entire deployment eventually works great.

Something is wrong in the auto-creation scripts for the cloud environment. It needs to have an AMI type selected. Otherwise it defaults to 14.0 and it breaks. If that's the goal, then something in 14.0 and BIG-IQ needs to be fixed.

Deploying per app VE (LTM module)

If I would like to deploy the per app ve (LTM module) instead of WAF module for cloud edition on the AWS environment, which template should I select? Is there any concern regarding to the configuration comparing with WAF? Or more or less the same

Thank you.

Azure: SSG in paused state

Dear team,
I have deployed the "existing VNET/no demo app" ARM template, but unfortunately the SSG isn't coming up. I see the following error in /var/log/restjavad.0.log

[INFO][04 Feb 2019 13:14:38 PST][/cm/cloud/tasks/azure/initial-buildout/18f897df-44e2-4a5a-b9b1-ef34a832a4fc/worker InitialBuildOutTaskWorker] Polling: /mgmt/cm/cloud/orchestrator/azure/tasks/deploy-auto-scale/9d4867e8-2b99-4df5-8443-5b0c2fdd5a4f
[INFO][04 Feb 2019 13:14:38 PST][/cm/cloud/azure/images-info ImagesInfoWorker] Completed the retrieval of images list.
[WARN][04 Feb 2019 13:14:48 PST][/cm/cloud/tasks/azure/initial-buildout/18f897df-44e2-4a5a-b9b1-ef34a832a4fc/worker InitialBuildOutTaskWorker] java.lang.Exception: Failed to trigger the flask task: java.lang.IllegalStateException: Deploying ARM template failed: Deployment failed for azure-ssg. Reason: Deployment failed with status code: 400 and message: The template deployment 'azure-ssg' is not valid according to the validation procedure. The tracking id is '4fe73c7a-6dc9-4d60-9320-3dd7bb50c0f9'. See inner errors for details. Please see https://aka.ms/arm-deploy for usage details.
	at com.f5.rest.workers.cloud.task.FlaskUtils$2.completed(FlaskUtils.java:144)
	at com.f5.rest.workers.cloud.task.FlaskUtils$2.completed(FlaskUtils.java:119)
	at com.f5.rest.common.RestOperation.complete(RestOperation.java:2711)
	at com.f5.rest.common.ApacheAsyncRequestSender.lambda$completeRequestOnNonBlockingPool$5(ApacheAsyncRequestSender.java:374)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

	at com.f5.rest.workers.cloud.task.azure.step.CreateVMTask$1.failed(CreateVMTask.java:69)
	at com.f5.rest.workers.cloud.task.azure.step.CreateVMTask$1.failed(CreateVMTask.java:60)
	at com.f5.rest.workers.cloud.task.FlaskUtils$2.completed(FlaskUtils.java:144)
	at com.f5.rest.workers.cloud.task.FlaskUtils$2.completed(FlaskUtils.java:119)
	at com.f5.rest.common.RestOperation.complete(RestOperation.java:2711)
	at com.f5.rest.common.ApacheAsyncRequestSender.lambda$completeRequestOnNonBlockingPool$5(ApacheAsyncRequestSender.java:374)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

[ERROR][04 Feb 2019 13:14:48 PST][/cm/cloud/tasks/azure/initial-buildout/18f897df-44e2-4a5a-b9b1-ef34a832a4fc/worker InitialBuildOutTaskWorker] java.lang.Exception: Failed to trigger the flask task: java.lang.IllegalStateException: Deploying ARM template failed: Deployment failed for azure-ssg. Reason: Deployment failed with status code: 400 and message: The template deployment 'azure-ssg' is not valid according to the validation procedure. The tracking id is '4fe73c7a-6dc9-4d60-9320-3dd7bb50c0f9'. See inner errors for details. Please see https://aka.ms/arm-deploy for usage details.
	at com.f5.rest.workers.cloud.task.FlaskUtils$2.completed(FlaskUtils.java:144)
	at com.f5.rest.workers.cloud.task.FlaskUtils$2.completed(FlaskUtils.java:119)
	at com.f5.rest.common.RestOperation.complete(RestOperation.java:2711)
	at com.f5.rest.common.ApacheAsyncRequestSender.lambda$completeRequestOnNonBlockingPool$5(ApacheAsyncRequestSender.java:374)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

	at com.f5.rest.workers.cloud.task.azure.step.CreateVMTask$1.failed(CreateVMTask.java:69)
	at com.f5.rest.workers.cloud.task.azure.step.CreateVMTask$1.failed(CreateVMTask.java:60)
	at com.f5.rest.workers.cloud.task.FlaskUtils$2.completed(FlaskUtils.java:144)
	at com.f5.rest.workers.cloud.task.FlaskUtils$2.completed(FlaskUtils.java:119)
	at com.f5.rest.common.RestOperation.complete(RestOperation.java:2711)
	at com.f5.rest.common.ApacheAsyncRequestSender.lambda$completeRequestOnNonBlockingPool$5(ApacheAsyncRequestSender.java:374)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

[ERROR][04 Feb 2019 13:14:48 PST][/cm/cloud/tasks/azure/initial-buildout/18f897df-44e2-4a5a-b9b1-ef34a832a4fc/worker InitialBuildOutTaskWorker] Reject reentrant transition to status FAILED - java.lang.IllegalStateException
	at com.f5.rest.workers.configmgmtbase.task.BaseTaskWorker.endsReentrance(BaseTaskWorker.java:1136)
	at com.f5.rest.workers.configmgmtbase.task.BaseTaskWorker.allowedUpdate(BaseTaskWorker.java:1081)
	at com.f5.rest.workers.configmgmtbase.task.BaseTaskWorker.updateTaskStatus(BaseTaskWorker.java:981)
	at com.f5.rest.workers.configmgmtbase.task.BaseTaskWorker.updateStatus(BaseTaskWorker.java:921)
	at com.f5.rest.workers.configmgmtbase.task.BaseTaskWorker.updateStatus(BaseTaskWorker.java:943)
	at com.f5.rest.workers.cloud.task.azure.buildout.InitialBuildOutTaskWorker.updateStep(InitialBuildOutTaskWorker.java:236)
	at com.f5.rest.workers.cloud.task.azure.buildout.InitialBuildOutTaskWorker.access$200(InitialBuildOutTaskWorker.java:43)
	at com.f5.rest.workers.cloud.task.azure.buildout.InitialBuildOutTaskWorker$7.completed(InitialBuildOutTaskWorker.java:342)
	at com.f5.rest.workers.cloud.task.azure.buildout.InitialBuildOutTaskWorker$7.completed(InitialBuildOutTaskWorker.java:339)
	at com.f5.rest.workers.cloud.task.azure.BaseAzureTaskWorker$7.completed(BaseAzureTaskWorker.java:370)
	at com.f5.rest.workers.cloud.task.azure.BaseAzureTaskWorker$7.completed(BaseAzureTaskWorker.java:367)
	at com.f5.rest.common.RestOperation.complete(RestOperation.java:2711)
	at com.f5.rest.common.RestWorker$3.completed(RestWorker.java:685)
	at com.f5.rest.common.RestWorker$3.completed(RestWorker.java:678)
	at com.f5.rest.common.RestOperation.complete(RestOperation.java:2711)
	at com.f5.rest.common.RestCollectionWorker$18.completed(RestCollectionWorker.java:1879)
	at com.f5.rest.common.RestCollectionWorker$18.completed(RestCollectionWorker.java:1875)
	at com.f5.rest.common.RestWorker.indexCreateOrReplaceItem(RestWorker.java:1821)
	at com.f5.rest.common.RestCollectionWorker.handlePatchEvent(RestCollectionWorker.java:1875)
	at com.f5.rest.common.RestCollectionWorker.access$1300(RestCollectionWorker.java:59)
	at com.f5.rest.common.RestCollectionWorker$16.completed(RestCollectionWorker.java:1811)
	at com.f5.rest.common.RestCollectionWorker$16.completed(RestCollectionWorker.java:1805)
	at com.f5.rest.common.RestOperation.complete(RestOperation.java:2711)
	at com.f5.rest.workers.storage.StorageWorker$9.completed(StorageWorker.java:890)
	at com.f5.rest.workers.storage.StorageWorker$9.completed(StorageWorker.java:885)
	at com.f5.rest.workers.storage.TransactionRunnable$TxRunCompletion.run(TransactionRunnable.java:644)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

[WARN][04 Feb 2019 13:14:48 PST][/cm/cloud/tasks/azure/initial-buildout/18f897df-44e2-4a5a-b9b1-ef34a832a4fc/worker InitialBuildOutTaskWorker] Reentrant update, dropping update to status FAILED

Thanks & br
Daniel

Setup Ubuntu template missing some ami id's for some regions (Tokyo, etc.)

ISSUE TYPE
  • Bug Report
COMPONENT NAME

(https://s3.amazonaws.com/big-iq-quickstart-cf-templates/6.0.0/Setup-Ubuntu-Trial.template)

SUMMARY

When trying to launch the CFT in the tokyo region (ap-northeast-1), stack launch fails because unable to map to a tokyo region ami id for ubuntu. This isn't listed in the CFT for Setup-Ubuntu-Trial.template.

"Unable to get mapping for AWSRegionArch2AMI::ap-northeast-1::64"

Tokyo Region ubuntu 16.0.4:
Ubuntu Server 16.04 LTS (HVM), SSD Volume Type - ami-940cdceb

STEPS TO REPRODUCE
  1. Click Launch button here: https://github.com/f5devcentral/f5-big-ip-cloud-edition-trial-quick-start
  2. Attempt to launch in Tokyo region
  3. confirm failure in events.
WORKAROUND ATTEMPTED
  1. Download both nested template "Setup-Ubuntu-Trial.template" and the "bigiq-cm-dcd-pair-with-ssg.template"
  2. Modify the "Setup-Ubuntu-Trial.template" with the ami id for Ubuntu in tokyo region
  3. UPload the modified "Setup-Ubuntu-Trial.template" to S3 and make read only
  4. Modify "bigiq-cm-dcd-pair-with-ssg.template" to point to the location of the modified "Setup-Ubuntu-Trial.template"
  5. Upload stack to AWS and launch
EXPECTED RESULTS

CFT to deploy in Tokyo region

ACTUAL RESULTS

Failed to launch stack

Template error: Unable to get mapping for AWSRegionArch2AMI::ap-northeast-1::64

image

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.