action #461: Amazon EC2 - openSUSE 13.1 Release - openSUSE Project Management Tool

Custom queries

openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QE tools team - backlog (ready issues)
QE tools team - backlog (w/o infra)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (w/o infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

action #461

closed

action #460: For each cloud, describe how to get an account on there

Amazon EC2

Added by Anonymous almost 11 years ago. Updated over 10 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Marketing

Target version:

13.1 GA

Start date:

2013-08-15

Due date:

2013-11-05

% Done:

100%

Estimated time:

Description

describe how to get an account on there

History
Notes
Property changes

Actions

Copy link

Updated by Anonymous almost 11 years ago

% Done changed from 0 to 100
Status changed from In Progress to Resolved

From Robert Schweikert:
We SUSE, possibly the openSUSE Team, should publish openSUSE images to EC2, I think. We do have a number of accounts in EC2 that have consolidated billing, i.e. SUSE pays the bill. I suggest that we add and account that can be shared by the openSUSE team and that this account be used to publish the images.

You can contact Pete Chadwick, PM for Cloud, about getting an account. Once the account is setup you should be able to integrate this relatively easily into the release process.

We build the images for SLES we have in EC2 in IBS, we could use a similar setup for the openSUSE images in OBS, let me know if I can help with this.

Actions

Copy link

Updated by toscalix over 10 years ago

Category set to Marketing
Status changed from Resolved to Feedback
Assignee set to Anonymous

Please add information about what will be done for 13.1. Did you already include this effort in the release process? Robert needs to be pinged about this the right day. If we can include the image on time for the release, we should also announce it. What do you think?

Actions

Copy link

Updated by Anonymous over 10 years ago

We can and should of course mention this in the release announcement if it is done, yes. If we do it, who does it, how to do it - I think that is a question for whoever controls the technical release process, not a question for marketing...

Actions

Copy link

Updated by Anonymous over 10 years ago

Status changed from Feedback to Resolved

Actions

Copy link

Updated by toscalix over 10 years ago

Status changed from Resolved to In Progress

Robert will do the technical work. Yo simply need to make sure is done before we publish the announcement and include on it the instructions to use it from there.

Talk to him also when the release is coming about other possible clouds where openSUSE can be deployed by him so we can include them in the announcement and social media

Actions

Copy link