[auto-scaling][self-healing] Discussion to merge two SIG to one
Dear all
As we discussed in PTG about merge two SIG to one. I would like to continue the discussion on ML.
In PTG, Eric proposes the idea to merge two SIG due to the high overlapping of domains and tasks.
I think this is a great idea since, over the last 6 months, most of the discussions in both SIG are overlapped. So I'm onboard with this idea.
Here's how I think we can continue this idea:
1. Create new SIG (maybe 'Automation SIG'? feel free to propose name which can cover both interest.) 2. Redirect docs and wiki to new SIG. And rework on index so there will be no confusion 3. Move repos from both SIGs to new SIG 4. Mark auto-scaling SIG and self-healing SIG as inactive. 5. remove auto-scaling SIG and self-healing SIG after a reasonable waiting time
Let us know what you think about this. Otherwise, we definitely expect this to happen soon.
Hi Rico,
+1 That is a very good idea. Coincidentally, I'm working on some research projects that focus on autoscaling and self-healing at the same time. And the combined group would be a very good idea because I don't have to switch back and forth between the groups for discussion.
Thanks,
On Thu, Nov 21, 2019 at 12:57 AM Rico Lin rico.lin.guanyu@gmail.com wrote:
Dear all
As we discussed in PTG about merge two SIG to one. I would like to continue the discussion on ML.
In PTG, Eric proposes the idea to merge two SIG due to the high overlapping of domains and tasks.
I think this is a great idea since, over the last 6 months, most of the discussions in both SIG are overlapped. So I'm onboard with this idea.
Here's how I think we can continue this idea:
- Create new SIG (maybe 'Automation SIG'? feel free to propose name
which can cover both interest.) 2. Redirect docs and wiki to new SIG. And rework on index so there will be no confusion 3. Move repos from both SIGs to new SIG 4. Mark auto-scaling SIG and self-healing SIG as inactive. 5. remove auto-scaling SIG and self-healing SIG after a reasonable waiting time
Let us know what you think about this. Otherwise, we definitely expect this to happen soon.
-- May The Force of OpenStack Be With You,
*Rico Lin*irc: ricolin
+1 from me.
On Thu, Nov 21, 2019 at 3:21 PM Trinh Nguyen dangtrinhnt@gmail.com wrote:
Hi Rico,
+1 That is a very good idea. Coincidentally, I'm working on some research projects that focus on autoscaling and self-healing at the same time. And the combined group would be a very good idea because I don't have to switch back and forth between the groups for discussion.
Thanks,
On Thu, Nov 21, 2019 at 12:57 AM Rico Lin rico.lin.guanyu@gmail.com wrote:
Dear all
As we discussed in PTG about merge two SIG to one. I would like to continue the discussion on ML.
In PTG, Eric proposes the idea to merge two SIG due to the high overlapping of domains and tasks.
I think this is a great idea since, over the last 6 months, most of the discussions in both SIG are overlapped. So I'm onboard with this idea.
Here's how I think we can continue this idea:
- Create new SIG (maybe 'Automation SIG'? feel free to propose name
which can cover both interest.) 2. Redirect docs and wiki to new SIG. And rework on index so there will be no confusion 3. Move repos from both SIGs to new SIG 4. Mark auto-scaling SIG and self-healing SIG as inactive. 5. remove auto-scaling SIG and self-healing SIG after a reasonable waiting time
Let us know what you think about this. Otherwise, we definitely expect this to happen soon.
-- May The Force of OpenStack Be With You,
*Rico Lin*irc: ricolin
-- *Trinh Nguyen* *www.edlab.xyz https://www.edlab.xyz*
Hi Rico and others,
Please let me know what I could do to help this process.
Bests,
On Fri, Nov 22, 2019 at 10:23 AM Duc Truong duc.openstack@gmail.com wrote:
+1 from me.
On Thu, Nov 21, 2019 at 3:21 PM Trinh Nguyen dangtrinhnt@gmail.com wrote:
Hi Rico,
+1 That is a very good idea. Coincidentally, I'm working on some research projects that focus on autoscaling and self-healing at the same time. And the combined group would be a very good idea because I don't have to switch back and forth between the groups for discussion.
Thanks,
On Thu, Nov 21, 2019 at 12:57 AM Rico Lin rico.lin.guanyu@gmail.com wrote:
Dear all
As we discussed in PTG about merge two SIG to one. I would like to continue the discussion on ML.
In PTG, Eric proposes the idea to merge two SIG due to the high overlapping of domains and tasks.
I think this is a great idea since, over the last 6 months, most of the discussions in both SIG are overlapped. So I'm onboard with this idea.
Here's how I think we can continue this idea:
- Create new SIG (maybe 'Automation SIG'? feel free to propose name
which can cover both interest.) 2. Redirect docs and wiki to new SIG. And rework on index so there will be no confusion 3. Move repos from both SIGs to new SIG 4. Mark auto-scaling SIG and self-healing SIG as inactive. 5. remove auto-scaling SIG and self-healing SIG after a reasonable waiting time
Let us know what you think about this. Otherwise, we definitely expect this to happen soon.
-- May The Force of OpenStack Be With You,
*Rico Lin*irc: ricolin
-- *Trinh Nguyen* *www.edlab.xyz https://www.edlab.xyz*
On 11/22/19 12:20 AM, Trinh Nguyen wrote:
Hi Rico,
+1 That is a very good idea. Coincidentally, I'm working on some research projects that focus on autoscaling and self-healing at the same time. And the combined group would be a very good idea because I don't have to switch back and forth between the groups for discussion.
Thanks,
On Thu, Nov 21, 2019 at 12:57 AM Rico Lin <rico.lin.guanyu@gmail.com mailto:rico.lin.guanyu@gmail.com> wrote:
Dear all As we discussed in PTG about merge two SIG to one. I would like to continue the discussion on ML. In PTG, Eric proposes the idea to merge two SIG due to the high overlapping of domains and tasks. I think this is a great idea since, over the last 6 months, most of the discussions in both SIG are overlapped. So I'm onboard with this idea. Here's how I think we can continue this idea: 1. Create new SIG (maybe 'Automation SIG'? feel free to propose name which can cover both interest.) 2. Redirect docs and wiki to new SIG. And rework on index so there will be no confusion 3. Move repos from both SIGs to new SIG 4. Mark auto-scaling SIG and self-healing SIG as inactive. 5. remove auto-scaling SIG and self-healing SIG after a reasonable waiting time
Hi, how about starting with joining the SIGs meeting times and organizing the Forum and PTG events together? The repositories and wiki pages could stay as they are and refer to each other.
Merging the content into one new repository definitely also has value but you should think how to structure it so that the users can find useful information quickly.
I think merging is good if you have an idea how to better structure the content, and time to review the existing one and do all the formal stuff. Just gluing the documents won't help.
Cheers Witek
On Thu, Nov 28, 2019 at 4:37 PM Witek Bedyk witold.bedyk@suse.com wrote:
Hi, how about starting with joining the SIGs meeting times and organizing the Forum and PTG events together? The repositories and wiki pages could stay as they are and refer to each other.
I think even if we merged two SIG, repositories should stay separated as they're now. IMO we can simply rename openstack/auto-scaling-sig to openstack/auto-scaling and so as to self-healing. Or just keep it the same will be fine IMO. We don't need a new repo for the new SIG (at least not for now).
I do like the idea to start with joining the SIGs meeting times and organizing the Forum and PTG events together. One more proposal in my mind will be, join the channel for IRC.
I think merging is good if you have an idea how to better structure the content, and time to review the existing one and do all the formal stuff. Just gluing the documents won't help.
Totally agree with this point!
Cheers Witek
-- May The Force of OpenStack Be With You, Rico Lin irc: ricolin
To further push this task. I would like to propose we pick a new joint meeting schedule for both SIGs together.
The first steps should be we share same meeting time and schedule, also share same event plan (as Witek suggested). And we can go from there to discuss if we need further plans. I also would like to suggest we move our meeting place to #openstack-meeting so we can have chance to have more people to join. Let's have a quick doodle polling for time, https://doodle.com/poll/98nrf8iibr7zv3kt Please join that doodle survey if you're interested in join us:)
On Thu, Nov 28, 2019 at 4:57 PM Rico Lin rico.lin.guanyu@gmail.com wrote:
On Thu, Nov 28, 2019 at 4:37 PM Witek Bedyk witold.bedyk@suse.com wrote:
Hi, how about starting with joining the SIGs meeting times and organizing the Forum and PTG events together? The repositories and wiki pages could stay as they are and refer to each other.
I think even if we merged two SIG, repositories should stay separated as they're now. IMO we can simply rename openstack/auto-scaling-sig to openstack/auto-scaling and so as to self-healing. Or just keep it the same will be fine IMO. We don't need a new repo for the new SIG (at least not for now).
I do like the idea to start with joining the SIGs meeting times and organizing the Forum and PTG events together. One more proposal in my mind will be, join the channel for IRC.
I think merging is good if you have an idea how to better structure the content, and time to review the existing one and do all the formal stuff. Just gluing the documents won't help.
Totally agree with this point!
Cheers Witek
-- May The Force of OpenStack Be With You, Rico Lin irc: ricolin
Hi guys, I send out a new schedule patch [1], please take a look to see if that works for you.
Which proposed 2020/01/07 Tuesday 1400 UTC on irc #openstack-meeting as our first combined meeting schedule.
[1] https://review.opendev.org/701137
On Wed, Dec 18, 2019 at 11:46 AM Rico Lin rico.lin.guanyu@gmail.com wrote:
To further push this task. I would like to propose we pick a new joint meeting schedule for both SIGs together.
The first steps should be we share same meeting time and schedule, also share same event plan (as Witek suggested). And we can go from there to discuss if we need further plans. I also would like to suggest we move our meeting place to #openstack-meeting so we can have chance to have more people to join. Let's have a quick doodle polling for time, https://doodle.com/poll/98nrf8iibr7zv3kt Please join that doodle survey if you're interested in join us:)
On Thu, Nov 28, 2019 at 4:57 PM Rico Lin rico.lin.guanyu@gmail.com wrote:
On Thu, Nov 28, 2019 at 4:37 PM Witek Bedyk witold.bedyk@suse.com wrote:
Hi, how about starting with joining the SIGs meeting times and organizing the Forum and PTG events together? The repositories and wiki pages could stay as they are and refer to each other.
I think even if we merged two SIG, repositories should stay separated as they're now. IMO we can simply rename openstack/auto-scaling-sig to openstack/auto-scaling and so as to self-healing. Or just keep it the same will be fine IMO. We don't need a new repo for the new SIG (at least not for now).
I do like the idea to start with joining the SIGs meeting times and organizing the Forum and PTG events together. One more proposal in my mind will be, join the channel for IRC.
I think merging is good if you have an idea how to better structure the content, and time to review the existing one and do all the formal stuff. Just gluing the documents won't help.
Totally agree with this point!
Cheers Witek
-- May The Force of OpenStack Be With You, Rico Lin irc: ricolin
-- May The Force of OpenStack Be With You,
*Rico Lin*irc: ricolin
participants (4)
-
Duc Truong
-
Rico Lin
-
Trinh Nguyen
-
Witek Bedyk